Closed Bug 905177 Opened 11 years ago Closed 10 years ago

Intermittent Ubuntu debug reftest "command timed out: 7200 seconds elapsed, attempting to kill"

Categories

(Testing :: Reftest, defect)

Product:
Testing
Component:
Reftest
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

Details

(Keywords: intermittent-failure) 

Ubuntu VM 12.04 fx-team debug test reftest on 2013-08-12 18:40:16 PDT for push 7c461e6aea7f

slave: tst-linux32-ec2-027

https://tbpl.mozilla.org/php/getParsedLog.php?id=26467293&tree=Fx-Team#error0

{
20:40:21     INFO -  REFTEST TEST-START | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-dashed-quirks.html
20:40:21     INFO -  REFTEST TEST-LOAD | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-dashed-quirks.html | 8826 / 9473 (93%)
20:40:21     INFO -  ++DOMWINDOW == 65 (0xbfd4a98) [serial = 24952] [outer = 0xaaa3938]
20:40:21     INFO -  REFTEST TEST-PASS | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-dashed-quirks.html | image comparison (!=)
20:40:21     INFO -  REFTEST INFO | Loading a blank page
20:40:21     INFO -  ++DOMWINDOW == 66 (0xb8a4d58) [serial = 24953] [outer = 0xaaa3938]
20:40:21     INFO -  REFTEST TEST-END | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-dashed-quirks.html
20:40:21     INFO -  REFTEST TEST-START | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-double-quirks.html
20:40:21     INFO -  REFTEST TEST-LOAD | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-double-quirks.html | 8827 / 9473 (93%)
20:40:21     INFO -  ++DOMWINDOW == 67 (0xb0265c8) [serial = 24954] [outer = 0xaaa3938]
20:40:21     INFO -  REFTEST TEST-PASS | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-double-quirks.html | image comparison (!=)
20:40:21     INFO -  REFTEST INFO | Loading a blank page
20:40:21     INFO -  ++DOMWINDOW == 68 (0xbbc5ac8) [serial = 24955] [outer = 0xaaa3938]
20:40:22     INFO -  REFTEST TEST-END | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-double-quirks.html
20:40:22     INFO -  REFTEST TEST-START | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-wavy-quirks.html
20:40:22     INFO -  REFTEST TEST-LOAD | file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/text-decoration/overline-style-block-wavy-quirks.html | 8828 / 9473 (93%)
20:40:22     INFO -  ++DOMWINDOW == 69 (0xbe3f3a0) [serial = 24956] [outer = 0xaaa3938]

command timed out: 7200 seconds elapsed, attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=7200.011907
========= Finished '/tools/buildbot/bin/python scripts/scripts/desktop_unittest.py ...' failed (results: 2, elapsed: 2 hrs, 1 secs) (at 2013-08-12 20:40:23.341936) =========
}
Note: Green Ubuntu debug reftest runs typically take 113-114 mins, so we're pretty close to the max runtime limit of 120 mins on normal runs.
Would be curious to know if we've regressed runtime significantly recently
Huh this (recent) green one only took 102 mins:
https://tbpl.mozilla.org/php/getParsedLog.php?id=26531368&tree=Mozilla-Central
(Sorry spam)
Was more recent than the failures
Two things:
a) Runtime seems to vary quite a bit (guessing depends on which EC2 machine, since underlying hardware can vary).
b) Runtimes leading up to the weekend just gone were more in the 88-96 min range (looking at 10 green runs).
(In reply to Ed Morley [:edmorley UTC+1] from comment #6)
> b) Runtimes leading up to the weekend just gone were more in the 88-96 min
> range (looking at 10 green runs).

Does a retrigger today of those runs produce the same results?  i.e., was it a change in hardware or a change in our code?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Mass-closing intermittent-failure bugs filed by me, that have not occurred recently and do not have the leave-open keyword set.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.