Closed Bug 527069 Opened 11 years ago Closed 8 years ago

sporadic crash in test_attrgetownerelement01.html

Categories

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

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: dholbert, Unassigned)

References

Details

(Keywords: intermittent-failure)

{
0 INFO Running tests in tests/dom/tests/mochitest/dom-level2-core, tests/dom/tests/mochitest/dom-level2-html, tests/dom/tests/mochitest/general, tests/dom/tests/mochitest/geolocation, tests/dom/tests/mochitest/localstorage, tests/dom/tests/mochitest/sessionstorage, tests/dom/tests/mochitest/whatwg, tests/editor/composer/test, tests/editor/libeditor/base/tests, tests/editor/libeditor/html/tests, tests/editor/libeditor/text/tests, tests/embedding/test, tests/extensions/cookie/test, tests/extensions/universalchardet/tests
1 INFO SimpleTest START
2 INFO Running /tests/dom/tests/mochitest/dom-level2-core/test_attrgetownerelement01.html...
++DOMWINDOW == 13 (0xe1ce620) [serial = 14] [outer = 0xe068370]
}
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1257532039.1257533407.9591.gz
OS X 10.5.2 mozilla-central debug test mochitests-3/5 on 2009/11/06 10:27:19

This appears to be sporadic -- the only "guilty-range" changeset for this failure is a tests-only patch:  http://hg.mozilla.org/mozilla-central/rev/c6e8c9620f41
OS: Linux → Mac OS X
Whiteboard: [orange]
Sorry, my copy-paste in comment 0 missed the last few lines of the log (the actual timeout :))

{
2 INFO Running /tests/dom/tests/mochitest/dom-level2-core/test_attrgetownerelement01.html...
++DOMWINDOW == 13 (0xe1ce620) [serial = 14] [outer = 0xe068370]
--DOMWINDOW == 12 (0xe528690) [serial = 13] [outer = 0xe068370] [url = about:blank]

command timed out: 1200 seconds without output, killing pid 402
process killed by signal 9
program finished with exit code -1
}
Summary: sporadic timeout in test_attrgetownerelement01.html → sporadic crash in test_attrgetownerelement01.html
This bug was observed only on one or more of the six machines listed in
bug 787281 comment 11, which seem likely to have bad memory, disk, or
other hardware problem, based on the rate of failures on those machines
and the types of failures observed.

Therefore I'm marking this bug invalid, though it should be reopened if
it occurs on other (more reliable) hardware.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Whiteboard: [orange]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.