8 tests take ~50% of mir_acceptance_tests runtime

[Kevin DuBois]

[ OK ] ApplicationNotRespondingDetection.failure_to_pong_is_noticed (2008 ms)
[ OK ] ApplicationNotRespondingDetection.responding_client_is_not_marked_as_unresponsive (3010 ms)
[ OK ] ApplicationNotRespondingDetection.unresponsive_client_stops_receiving_pings (3015 ms)
[ OK ] ClientLogging.reports_performance (3018 ms)
[ OK ] ClientLatency.triple_buffered_client_has_less_than_two_frames_latency (1691 ms)
[ OK ] ClientLatency.latency_is_limited_to_nbuffers (1697 ms)
[ OK ] ClientLatency.throttled_input_rate_yields_lower_latency (1708 ms)
[ OK ] RaiseSurfaces.older_timestamp_does_not_focus (1036 ms)

total runtime for me is ~35s, these 8 tests take up ~17s runtime. Hopefully there would be a way for some of these tests to succeed more quickly.

[Daniel van Vugt (vanvugt)]

This is going to be an indefinitely recurring problem, but I can see it is annoying for test-driven development.

At some stage, you will need system tests or acceptance tests that cover the code in more real-world real-time scenarios. And such tests will take at least a few seconds each.

While we can tweak the above tests and maybe make them a little shorter, as the code matures and gains more test coverage, the problem will only grow. So try to optimize tests yes, but logging this as a bug is probably not a good idea because it will keep recurring indefinitely.

[Michał Sawicz (saviq)]

Syncing task from Mir.