Ok, it's hard to say what's going on, but... we're having problems with otto autopilot testing of the unity stack, only on the ati machine.
13:55 < sil2100> didrocks: sooo, mhr3 did some research and we think we're encountering the same recordmydesktop issue as before (which caused jibel to disable it) - but this time only on ati
13:56 < sil2100> didrocks: mhr3 ran unity AP tests on his ati machine in his office and there was all fine, ~17 failures he had - he's re running it
13:56 < sil2100> didrocks: we had 13 failures on intel
The system stops with this message, hanging:
E: Test failed to run in 7200 seconds. Aborting!
Ok, it's hard to say what's going on, but... we're having problems with otto autopilot testing of the unity stack, only on the ati machine.
13:55 < sil2100> didrocks: sooo, mhr3 did some research and we think we're encountering
the same recordmydesktop issue as before (which caused jibel to disable
it) - but this time only on ati
there was all fine, ~17 failures he had - he's re running it
13:56 < sil2100> didrocks: mhr3 ran unity AP tests on his ati machine in his office and
13:56 < sil2100> didrocks: we had 13 failures on intel
The system stops with this message, hanging:
E: Test failed to run in 7200 seconds. Aborting!
There seem to be issues with attaching to the container. Best to see the latest run: /jenkins. qa.ubuntu. com/job/ autopilot- saucy-daily_ release/ 575/label= autopilot- ati/console
https:/