Bugzilla

(In reply to Edgar Chen [:edgar] from comment #6)
> (In reply to Cosmin Sabou [:CosminS] from comment #3)
> > Redirecting this to Sean as per Bugbug. 
> > Pushlog between last good - first bad revision: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4024630f5ffa1704a32f70c816f1003b0af9f105&tochange=0be08aa0812f81d5eb9f2235165d8478ebaf825b
> 
> I cannot find some clue from pushlog, didn't see anything obvious.
> And I tried to find which commit might cause this, but I still see the test fails on [the last good revision](https://hg.mozilla.org/mozilla-central/rev/6931444dba7cd9968a1cd8b9b1f7c8daa63205ab) on my central-as-beta simulation try push, https://treeherder.mozilla.org/jobs?repo=try&revision=de84f0eacb4d7753fd906ad34cc4f06d3eecd608&selectedTaskRun=VpT9wUujQ7iFDERINmDNcA.0.
> So I wonder if this push log accurate. Can you share the last try that pass the test and also the first try link that you see this failure from your side, so I could try to find some clue from them? Thanks!

[Here](https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=QCAQkRCkQrKfNApM5fEDkg.0&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&revision=de5d65c3757a6740f25d3be54ff8d72ab6fe72fd&searchStr=os%2Cx%2C11%2Cwebrender%2Cshippable%2Copt%2Cmochitests%2Ctest-macosx1100-64-shippable-qr%2Fopt-mochitest-browser-chrome%2Cbc1&group_state=expanded) is the beta simulation run from the day before I found this. I've retriggered the job to see if it was perma failing on that run, and as you can see, it was not. The failed jobs from the link above, failed because of a high frequency failure that was happening that day, and if you check the logs for the failed jobs, you can see that [browser_fullscreen_window_open.js](https://treeherder.mozilla.org/logviewer?job_id=434172375&repo=try&lineNumber=3543-3560) was passing.
I've also checked the link you provided for your run, it is the same situation as a described above, the job failed but with another failure. [Here](https://treeherder.mozilla.org/logviewer?job_id=434495448&repo=try&lineNumber=3551-3568) is a link to a failure log from your run, the test is passing.

(In reply to Edgar Chen [:edgar] from comment #6)
> (In reply to Cosmin Sabou [:CosminS] from comment #3)
> > Redirecting this to Sean as per Bugbug. 
> > Pushlog between last good - first bad revision: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4024630f5ffa1704a32f70c816f1003b0af9f105&tochange=0be08aa0812f81d5eb9f2235165d8478ebaf825b
> 
> I cannot find some clue from pushlog, didn't see anything obvious.
> And I tried to find which commit might cause this, but I still see the test fails on [the last good revision](https://hg.mozilla.org/mozilla-central/rev/6931444dba7cd9968a1cd8b9b1f7c8daa63205ab) on my central-as-beta simulation try push, https://treeherder.mozilla.org/jobs?repo=try&revision=de84f0eacb4d7753fd906ad34cc4f06d3eecd608&selectedTaskRun=VpT9wUujQ7iFDERINmDNcA.0.
> So I wonder if this push log accurate. Can you share the last try that pass the test and also the first try link that you see this failure from your side, so I could try to find some clue from them? Thanks!

[This is a link](https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&revision=3b2396a08e80a5aae69b7a24ecbe900aaac661ba&searchStr=os%2Cx%2C11%2Cwebrender%2Cshippable%2Copt%2Cmochitests%2Ctest-macosx1100-64-shippable-qr%2Fopt-mochitest-browser-chrome%2Cbc1&selectedTaskRun=aJYxaUksS5yLTAzs_UR-Qw.0) where I found this.
[Here](https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=QCAQkRCkQrKfNApM5fEDkg.0&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&revision=de5d65c3757a6740f25d3be54ff8d72ab6fe72fd&searchStr=os%2Cx%2C11%2Cwebrender%2Cshippable%2Copt%2Cmochitests%2Ctest-macosx1100-64-shippable-qr%2Fopt-mochitest-browser-chrome%2Cbc1&group_state=expanded) is the beta simulation run from the day before I found this. I've retriggered the job to see if it was perma failing on that run, and as you can see, it was not. The failed jobs from the link above, failed because of a high frequency failure that was happening that day, and if you check the logs for the failed jobs, you can see that [browser_fullscreen_window_open.js](https://treeherder.mozilla.org/logviewer?job_id=434172375&repo=try&lineNumber=3543-3560) was passing.
I've also checked the link you provided for your run, it is the same situation as a described above, the job failed but with another failure. [Here](https://treeherder.mozilla.org/logviewer?job_id=434495448&repo=try&lineNumber=3551-3568) is a link to a failure log from your run, the test is passing.