Closed Bug 1302917 Opened 4 years ago Closed 4 years ago
_streamupdater .js | xpcshell return code: 0
58 bytes, text/x-review-board-request
You're going to see a *lot* of these, because chasing down bustage with freshly reimaged WinXP slaves I had to trigger hundreds of WinXP xpcshell runs. I just hope it's a real intermittent we just hadn't happened to file yet, and not more reimage bustage.
(In reply to Phil Ringnalda (:philor) from comment #1) > I just hope it's a real intermittent we just hadn't happened to file > yet, and not more reimage bustage. What's the best way to tell? Wait for a week or two and check the OrangeFactor link?
Or a day or two and sort by the "Test Machine" column and see if it's multiple failures on just a few machines. Or look at the test failure with more understanding than I would have, and say "hey, that would only happen if some registry value that's supposed to be set was missing/some directory couldn't be written to/some other machine setup thing I can't think of was true."
This seems block bug 1315386, I would like to take it
Priority: P5 → P2
Running try 1x time to see if the intermittent occurs https://treeherder.mozilla.org/#/jobs?repo=try&revision=bb0463e6474e07012a827819fd9473d171b67aa1
Just remove the callback which calls to next_test without waiting for running result
Comment on attachment 8813091 [details] Bug 1302917 - Call callback correctly to Fix intermittent test_streamupdater.js https://reviewboard.mozilla.org/r/94610/#review95124
Attachment #8813091 - Flags: review?(francois) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/22346c89219f Call callback correctly to Fix intermittent test_streamupdater.js r=francois
Thomas, thanks for fixing this. Good job!
You need to log in before you can comment on or make changes to this bug.