Treeherder Bug Filer Reporter
	Description • 7 years ago
treeherder

Filed by: bmaris [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=116302583&repo=mozilla-beta

https://firefox-ui-tests.s3.amazonaws.com/64b04308-2681-4f6f-9717-0991863b74d1/log_info.log

This failure started in Fx 55.0b11 and was encountered on multiple locales.

	Henrik Skupin [:whimboo][⌚️UTC+1]
	Comment 1 • 7 years ago

Nothing should have changed on beta. Make sure to check the machines that there are no other still open Firefox processes remaining.

	[SV Manager] Florin Mezei, QA (:FlorinMezei)
	Comment 5 • 7 years ago

(In reply to Henrik Skupin (:whimboo) [away 07/19 - 07/31] from comment #1)
> Nothing should have changed on beta. Make sure to check the machines that
> there are no other still open Firefox processes remaining.

Turns out you are right - no surprise :). While running the tests on beta-cdntest today for 55b13, there were 4 Windows machines which had Nightly still open (though there were no running jobs for Nightly). Update tests on all 4 machines failed with this error, while tests on the other machines passed with no problem. Sure enough, after manually closing the open Nightly window on all machines, then all tests passed on those machines.

	Henrik Skupin [:whimboo][⌚️UTC+1]
	Comment 8 • 7 years ago

(In reply to Florin Mezei, QA (:FlorinMezei) from comment #5)
> Turns out you are right - no surprise :). While running the tests on
> beta-cdntest today for 55b13, there were 4 Windows machines which had
> Nightly still open (though there were no running jobs for Nightly). Update
> tests on all 4 machines failed with this error, while tests on the other
> machines passed with no problem. Sure enough, after manually closing the
> open Nightly window on all machines, then all tests passed on those machines.

Good to know that this was the reason. Bad, that we are that late with those checks and cannot check anymore in Jenkins what caused the Nighly builds to stay open. 

I'm closing this bug as fixed, but feel free to reopen or file a new one if it happens again.

	Henrik Skupin [:whimboo][⌚️UTC+1]
	Comment 12 • 7 years ago

(In reply to OrangeFactor Robot from comment #11)
> 46 failures in 885 pushes (0.052 failures/push) were associated with this
> bug in the last 7 days. 

I don't know why more and more failures are starred for this but no-one fixes it as described earlier. Florin please make sure that people are aware of what's going on here. Thanks.

	[SV Manager] Florin Mezei, QA (:FlorinMezei)
	Comment 13 • 7 years ago

(In reply to Henrik Skupin (:whimboo) from comment #12)
> I don't know why more and more failures are starred for this but no-one
> fixes it as described earlier. Florin please make sure that people are aware
> of what's going on here. Thanks.

This was seen on OS X with two RC builds - and from what I see it was starred on beta-cdntest and release-cdntest. However I remember that it wasn't the same issue as Windows, as there were no open Firefox instances on the machines. We've worked around those by running the jobs with a different test package.

I don't think we'll encounter this again since OS X tests are currently blocked on Fx 57 by bug 1398741. If the bug gets fixed, and we encounter this again, I'll instruct people to file a new bug for OS X.