Closed Bug 952053 Opened 11 years ago Closed 10 years ago

Intermittent TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\xpcshell\tests\modules\libpref\test\unit\test_libPrefs.js | Test timed out

Categories

(Core :: Preferences: Backend, defect)

Product:
Core
Component:
Preferences: Backend
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure)

Windows 7 32-bit mozilla-inbound debug test xpcshell on 2013-12-18 23:30:28 PST for push ccdc3d4f4571 slave: t-w732-ix-127 https://tbpl.mozilla.org/php/getParsedLog.php?id=32205214&tree=Mozilla-Inbound TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\xpcshell\tests\modules\libpref\test\unit\test_libPrefs.js | Test timed out TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\xpcshell\tests\modules\libpref\test\unit\test_libPrefs.js | test failed (with xpcshell return code: 15), see following log: 0:16:54 INFO - TEST-INFO | (xpcshell/head.js) | test MAIN run_test pending (1) 00:16:54 INFO - System JS : WARNING C:/slave/test/build/tests/xpcshell/tests/modules/libpref/test/unit/test_libPrefs.js:303 - octal literals and octal escape sequences are deprecated 00:16:54 INFO - System JS : WARNING C:/slave/test/build/tests/xpcshell/tests/modules/libpref/test/unit/test_libPrefs.js:303 - octal literals and octal escape sequences are deprecated 00:16:54 INFO - System JS : WARNING C:/slave/test/build/tests/xpcshell/tests/modules/libpref/test/unit/test_libPrefs.js:303 - octal literals and octal escape sequences are deprecated 00:16:54 INFO - System JS : ERROR (null):0 - uncaught exception: 2147500037
Component: XPConnect → Preferences: Backend
I'm so confused on this one. It started on mccr8's ICC patch landing yesterday and I couldn't manage to reproduce it earlier than that no matter how much I tried (and believe me, I did). But now it's still happening post-backout. Not sure what's going on :(
I relanded the first part (bug 937960) after there were no timeouts in a try run, but maybe this came back intermittently? Feel free to back me out again to see I guess... (I'm on PTO today.)
Also, it did keep happening post backout of my patch, until some other patch was backed out for an Android XPCshell timeout.
Yeah, that's the confusing part. I did throw a clobber in the mix around that time too, FWIW.
Weird. Maybe my try run got lucky, or maybe it interacts with something that landed since the last time I updated.
(In reply to Andrew McCreight [:mccr8] from comment #16) > Weird. Maybe my try run got lucky, or maybe it interacts with something > that landed since the last time I updated. Comment 13 is green. Backed out. https://hg.mozilla.org/integration/mozilla-inbound/rev/e9bab00a241e
I guess bug 937960 got merged over to FxTeam? The last 5 are all from there.
Something weird is definitely going on. In the pushes around https://tbpl.mozilla.org/?tree=Fx-Team&rev=70befb4cf2f4 we're getting the lib pref timeout, but manually inspecting the code I don't see my changes in there. It looks like that includes the pushes that landed it, then backed it out the first time.
It looks like it was permaorange on FxTeam from this innocuous looking change: https://hg.mozilla.org/integration/fx-team/rev/c3239da6de33 all the way until a much later merge.
I get this orange intermittently with my ICC patches: https://tbpl.mozilla.org/?tree=Try&rev=4edef94420c3 of course I also get it without my patches, on the same changeset: https://tbpl.mozilla.org/?tree=Try&rev=687bf7d70252 So that's a little baffling.
(Rather, that first on there is my patches without anything pref related)
Closing bugs where TBPLbot has previously commented, but have now not been modified for >3 months & do not contain the whiteboard strings for disabled/annotated tests or use the keyword leave-open. Filter on: mass-intermittent-bug-closure-2014-07
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.