Integration tests TestClientIPCRender.test_accelerated_render fails on Galaxy Nexus and Nexus4

[Chris Gagnon]

Description:
Integration test TestClientIPCRender.test_accelerated_render tests fails on phone (I have a galaxy nexus)

steps:
1. install mir from CI build http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-armhf-ci/136/artifact/work/output/*zip*/output.zip
2. run the command 'mir-integration-tests'

expect results:
all tests pass

Actual results:
tests fail

log:

[ RUN ] TestClientIPCRender.test_accelerated_render
__pthread_gettid -2
/tmp/buildd/mir-0.1.1/tests/integration-tests/client/test_client_render.cpp:389: Failure
Value of: render_accelerated_process->wait_for_termination().succeeded()
  Actual: false
Expected: true
/tmp/buildd/mir-0.1.1/tests/integration-tests/client/test_client_render.cpp:394: Failure
Value of: red_pattern.check(*region0)
  Actual: false
Expected: true
[ FAILED ] TestClientIPCRender.test_accelerated_render (5611 ms)
[ RUN ] TestClientIPCRender.test_accelerated_render_double
__pthread_gettid -2
/tmp/buildd/mir-0.1.1/tests/integration-tests/client/test_client_render.cpp:404: Failure
Value of: render_accelerated_process_double->wait_for_termination().succeeded()
  Actual: false
Expected: true
/tmp/buildd/mir-0.1.1/tests/integration-tests/client/test_client_render.cpp:408: Failure
Value of: red_pattern.check(*region0)
  Actual: false
Expected: true
/tmp/buildd/mir-0.1.1/tests/integration-tests/client/test_client_render.cpp:412: Failure
Value of: green_pattern.check(*region1)
  Actual: false
Expected: true
[ FAILED ] TestClientIPCRender.test_accelerated_render_double (809 ms)

[Daniel van Vugt (vanvugt)]

The failure is slightly different on Nexus4:

[ RUN ] TestClientIPCRender.test_accelerated_render
unknown file: Failure
C++ exception with description "Timeout while waiting for child to change state" thrown in the test body.
[ FAILED ] TestClientIPCRender.test_accelerated_render (1384463563304 ms)

[https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/93/console]

[Daniel van Vugt (vanvugt)]

I suspect this might have been fixed by:
    lp:~afrantzis/mir/fix-mako-ci-use-steady-clock

Particularly with the wacky time shown in comment #1.