Closed Bug 919110 Opened 12 years ago Closed 10 years ago

Intermittent TEST-UNEXPECTED-FAIL | scoped-style-011.html | application ran for longer than allowed maximum time

Categories

(Core :: CSS Parsing and Computation, defect, P5)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
All
Android
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=28184146&tree=Mozilla-Inbound slave: tegra-097 REFTEST TEST-START | http://10.250.49.160:30097/tests/layout/reftests/scoped-style/scoped-style-011.html REFTEST TEST-LOAD | http://10.250.49.160:30097/tests/layout/reftests/scoped-style/scoped-style-011.html | 1641 / 2276 (72%) REFTEST TEST-LOAD | http://10.250.49.160:30097/tests/layout/reftests/scoped-style/scoped-style-011-ref.html | 1641 / 2276 (72%) TEST-UNEXPECTED-FAIL | http://10.250.49.160:30097/tests/layout/reftests/scoped-style/scoped-style-011.html | application ran for longer than allowed maximum time INFO | automation.py | Application ran for: 1:01:21.765161 INFO | zombiecheck | Reading PID log: /tmp/tmpGW3mGEpidlog /data/anr/traces.txt not found WARNING | leakcheck | refcount logging is off, so leaks can't be detected!
It's hard to tell without timestamps on each line of the reftest log output, but it looks like the entire reftest suite is taking longer than an hour (seems like that's the limit?), rather than scoped-style-011.html itself timing out.
(In reply to Cameron McCormack (:heycam) from comment #1) > It's hard to tell without timestamps on each line of the reftest log output, > but it looks like the entire reftest suite is taking longer than an hour > (seems like that's the limit?), rather than scoped-style-011.html itself > timing out. https://bugzilla.mozilla.org/show_bug.cgi?id=919108 failed similarly. https://bugzilla.mozilla.org/show_bug.cgi?id=919104 crashed in a font reftest, unsure if that's related or just IPC weirdness.
Priority: -- → P5
Inactive; closing (see bug 1180138).
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.