Closed Bug 1089849 Opened 11 years ago Closed 9 years ago

Intermittent browser_bug1045809.js | Uncaught exception

Categories

(Core :: DOM: Security, defect)

Product:
Core
Component:
DOM: Security
Platform:
x86_64
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [domsecurity-backlog])

https://treeherder.mozilla.org/ui/logviewer.html#?job_id=533249&repo=mozilla-central builder Windows 8 64-bit mozilla-central opt test mochitest-e10s-browser-chrome-1 buildid 20141024170410 builduid c3e566eb0b514f7b99c7c07040fd6289 results warnings (1) revision e8a6f40728b7 slave t-w864-ix-107 starttime Fri Oct 24 2014 21:42:18 GMT-0400 (Eastern Standard Time)
Georgios, do you have time to investigate this?
Flags: needinfo?(georgios.kontaxis)
Tanvi, would this fall under your purview these days?
Flags: needinfo?(georgios.kontaxis) → needinfo?(tanvi)
The implementation of the code this test touches and the test itself changed in August. Since we have only one failure since then, maybe this is no longer an issue. cc'ing Brian in case he has any ideas. https://hg.mozilla.org/mozilla-central/diff/2e33ac0bb341/browser/base/content/test/general/browser_bug1045809.js https://dxr.mozilla.org/mozilla-central/source/browser/base/content/test/general/browser_bug1045809.js The error since the test changed also doesn't look like the other errors, and refers to something in this method. It may just be a synchronization issue: https://mxr.mozilla.org/mozilla-central/source/browser/base/content/test/general/head.js#589
Flags: needinfo?(bgrinstead)
Flags: needinfo?(tanvi)
(In reply to Tanvi Vyas [:tanvi] from comment #51) > The implementation of the code this test touches and the test itself changed > in August. Since we have only one failure since then, maybe this is no > longer an issue. cc'ing Brian in case he has any ideas. > > https://hg.mozilla.org/mozilla-central/diff/2e33ac0bb341/browser/base/ > content/test/general/browser_bug1045809.js > > https://dxr.mozilla.org/mozilla-central/source/browser/base/content/test/ > general/browser_bug1045809.js > > The error since the test changed also doesn't look like the other errors, > and refers to something in this method. It may just be a synchronization > issue: > https://mxr.mozilla.org/mozilla-central/source/browser/base/content/test/ > general/head.js#589 I have no idea why the load event would fail. This is an unlikely place for a test to fail, basically every test does something like that - it's just waiting for https://test1.example.com/browser/browser/base/content/test/general/file_bug1045809_1.html to load, which is earlier in the test than any of the recent changes happened [0]. This is the line where the failure is happening [1]. FWIW the revision this failed on was backed out, so maybe that has something to do with it? [2]. [0]: https://hg.mozilla.org/mozilla-central/diff/2e33ac0bb341/browser/base/content/test/general/browser_bug1045809.js [1]: https://dxr.mozilla.org/mozilla-central/source/browser/base/content/test/general/browser_bug1045809.js#25 [2]: https://hg.mozilla.org/integration/mozilla-inbound/rev/71886d218c12
Flags: needinfo?(bgrinstead)
Thanks for looking at this Brian! Given the one entry we have after the test changed is from a backed out change. And the rest of the errors are different and may relate to the old version of the code, I think we should ignore this for now and see if any other issues come up.
This intermittent failure hasn't been triggered in like 6 months. I think we can close this bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [domsecurity-backlog]
You need to log in before you can comment on or make changes to this bug.