Happened today on Linux 12.04 x64 with Aurora FR builds: http://mozmill-ci.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa063dcf91 It seems related to the http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?changeset=487982220b4e. Although if it were a regression, the issue should be able to be reproduced locally and also happen for other FF versions. It might be related to the machine (mm-ub-1204-64-3) having some issues. The console log is here: http://mm-ci-master.qa.scl3.mozilla.com:8080/job/mozilla-aurora_functional/3094/console
I can reproduce it locally in the restart tests, so it might be related to the changeset added above. Locally: http://mozmill-crowd.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa06421d9f Report from mozmill-ci when it happened: http://mozmill-ci.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa063e62b3 NOTE: I will try again to reproduce for non-restart tests, too.
I don't see why it should be related to the changeset http://hg.mozilla.org/releases/mozilla-aurora/rev/487982220b4e. Nothing in their changes anything related to the code in the affected areas in our tests. What about Nightly?
Functional tests did not run yet on Nightly. This seems to be related to the lock screen on Linux. When first testing with lock screen off - the functional errors did not reproduce: http://mozmill-crowd.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa06418e2e With lock screen on the issue reproduces every time: http://mozmill-crowd.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa0642606d Full pushlog is here: http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=840ca31cb3df&tochange=487982220b4e, I will try to use Tinderbox builds and see if there is another changeset that affected this
None of our machines have lock screen enabled. Means there might be something else which is affecting us here.
(In reply to Henrik Skupin (:whimboo) from comment #4) > None of our machines have lock screen enabled. Means there might be > something else which is affecting us here. This is the only way I was able to reproduce the issue locally. Also, the issue did not reproduce since 2nd of May on any machine.
Incomplete for now. If it happens again we need more information what happened on those machines. As of now there is no action to take.