Closed Bug 856024 Opened 11 years ago Closed 11 years ago

Intermittent test_browserElement_oop_Close.html,test_browserElement_oop_LoadEvents.html, and many other test_browserElement_oop_*.html tests | Exited with code -20 during test run

Categories

(Core :: DOM: Core & HTML, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=21239378&tree=Mozilla-Inbound

Rev5 MacOSX Mountain Lion 10.8 mozilla-inbound debug test mochitest-2 on 2013-03-29 01:37:31 PDT for push d9508b8cf262
slave: talos-mtnlion-r5-032

01:42:44     INFO -  --DOCSHELL 0x10454eaf0 == 1 [id = 2]
01:42:44     INFO -  --DOCSHELL 0x10457ca80 == 0 [id = 3]
01:42:44     INFO -  [Child 904] WARNING: NS_ENSURE_TRUE(compMgr) failed: file nsComponentManagerUtils.cpp, line 58
01:42:44     INFO -  nsStringStats
01:42:44     INFO -   => mAllocCount:          10450
01:42:44     INFO -   => mReallocCount:          380
01:42:44     INFO -   => mFreeCount:           10450
01:42:44     INFO -   => mShareCount:          13812
01:42:44     INFO -   => mAdoptCount:            652
01:42:44     INFO -   => mAdoptFreeCount:        652
01:42:44     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:44     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:44     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:44     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:44     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:44     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:45     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:45     INFO -  [Child 905] WARNING: Startup cache is only available in the chrome process: file ../../startupcache/StartupCache.cpp, line 93
01:42:45     INFO -  ###!!! [Child][SyncChannel] Error: Channel error: cannot send/recv
01:42:45     INFO -  [Child 905] WARNING: content process _exit()ing: file ../../../dom/ipc/ContentChild.cpp, line 968
01:42:45  WARNING -  TEST-UNEXPECTED-FAIL | /tests/dom/browser-element/mochitest/test_browserElement_oop_Close.html | Exited with code -20 during test run
https://tbpl.mozilla.org/php/getParsedLog.php?id=21249757&tree=Mozilla-Inbound
Summary: Intermittent test_browserElement_oop_Close.html | Exited with code -20 during test run → Intermittent test_browserElement_oop_Close.html,test_browserElement_oop_LoadEvents.html | Exited with code -20 during test run
https://tbpl.mozilla.org/php/getParsedLog.php?id=21259203&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=21262948&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=21263137&tree=Mozilla-Inbound
Summary: Intermittent test_browserElement_oop_Close.html,test_browserElement_oop_LoadEvents.html | Exited with code -20 during test run → Intermittent test_browserElement_oop_XYZ.html | Exited with code -20 during test run (for XYZ in {Close,LoadEvents,AlertInFrame,SetVisibleFrames,XFrameOptionsDeny,...})
https://tbpl.mozilla.org/php/getParsedLog.php?id=21262007&tree=Mozilla-Inbound
Summary: Intermittent test_browserElement_oop_XYZ.html | Exited with code -20 during test run (for XYZ in {Close,LoadEvents,AlertInFrame,SetVisibleFrames,XFrameOptionsDeny,...}) → Intermittent test_browserElement_oop_XYZ.html | Exited with code -20 during test run (for XYZ in {Close,LoadEvents,AlertInFrame,SetVisibleFrames,XFrameOptionsDeny,RemoveBrowserElement,...})
Changing the summary like that means that tbpl will never ever again find this bug for any failure in any test. Was that your plan?
Does this mean that a child process is dying, or that the parent process is dying?
(In reply to Phil Ringnalda (:philor) from comment #4)
> Was that your plan?

Nope.
 
I changed it because names of the recent failures didn't fit in the summary (since these test names are huge), but they seemed to be due to this bug. (And I thought TBPL's fuzzy-matching might apply to the test-names, like it does for error messages).  If the test name needs to match exactly, then I suppose we can file separate bugs for separate tests (or separate chunks of tests).
(For now, I'll just revert my bug-summary tweak, and mention "test_browserElement_oop_*.html" to indicate (to humans) that this affects lots of tests whose names match that pattern.)
Summary: Intermittent test_browserElement_oop_XYZ.html | Exited with code -20 during test run (for XYZ in {Close,LoadEvents,AlertInFrame,SetVisibleFrames,XFrameOptionsDeny,RemoveBrowserElement,...}) → Intermittent test_browserElement_oop_Close.html,test_browserElement_oop_LoadEvents.html, and many other test_browserElement_oop_*.html tests | Exited with code -20 during test run
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=test_browserElement_oop%2020%20kw%3Aintermittent - we have a *lot* of others that still have room left for another test name or two in the summary :)
I think essentially everything is going right here.  The child process's channel is closed, so it kills itself.

So offhand, I'd say we should exit(0) instead of exit(-20)'ing.  Let's see how bent feels about a patch.
> So offhand, I'd say we should exit(0) instead of exit(-20)'ing.  Let's see how bent feels about a 
> patch.

I misunderstood.  The child is _exit(0)'ing, and that's somehow causing the parent to crash with code -20.
Component: DOM: Mozilla Extensions → DOM
Blocks: 817247
Blocks: 819130
Blocks: 820318
Blocks: 820412
Blocks: 820749
Blocks: 832691
Blocks: 835590
Blocks: 835927
Blocks: 846098
Blocks: 866971
Blocks: 868310
Blocks: 872259
Blocks: 876304
Blocks: 877818
Depends on: 884471
Fixed (or worked around) by bug 884471.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.