Intermittent test_clearTimeouts.html | Fatal Python error: GC object already tracked | command timed out: 1200 seconds without output

RESOLVED INVALID

Status

Testing
General
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: emorley, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86_64
Mac OS X
intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Rev4 MacOSX Lion 10.7 mozilla-inbound debug test mochitests-4/5 on 2012-08-04 12:09:30 PDT for push 66f8a222e9bc

slave: talos-r4-lion-069

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

{
780 INFO TEST-START | /tests/dom/workers/test/test_blobWorkers.html
++DOMWINDOW == 44 (0x128d018c0) [serial = 139] [outer = 0x11647a290]
781 INFO TEST-PASS | /tests/dom/workers/test/test_blobWorkers.html | Got correct message - hi should equal hi
782 INFO TEST-END | /tests/dom/workers/test/test_blobWorkers.html | finished in 169ms
783 INFO TEST-START | /tests/dom/workers/test/test_chromeWorker.html
++DOMWINDOW == 45 (0x1121be320) [serial = 140] [outer = 0x11647a290]
784 INFO TEST-PASS | /tests/dom/workers/test/test_chromeWorker.html | ChromeWorker constructor wasn't blocked!
785 INFO TEST-END | /tests/dom/workers/test/test_chromeWorker.html | finished in 166ms
786 INFO TEST-START | /tests/dom/workers/test/test_clearTimeouts.html
++DOMWINDOW == 46 (0x13a7c95d0) [serial = 141] [outer = 0x11647a290]
Fatal Python error: GC object already tracked

command timed out: 1200 seconds without output, attempting to kill
process killed by signal 6
program finished with exit code -1
}
This looks like a test harness or buildbot issue ...
Component: DOM: Workers → General
Product: Core → Testing
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
Last Resolved: 6 years ago
Resolution: --- → INVALID
(Assignee)

Updated

6 years ago
Keywords: intermittent-failure
(Assignee)

Updated

6 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.