Closed Bug 889026 Opened 12 years ago Closed 11 years ago

Intermittent B2G test_property_database.html | application timed out after 330 seconds with no output

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

Details

(Keywords: intermittent-failure)

I'm worried this is just a matter of test_property_database being a huge test that we can't consistently run fast enough on B2G. Is there a way we can split this up or something? https://tbpl.mozilla.org/php/getParsedLog.php?id=24793837&tree=Mozilla-Inbound b2g_emulator_vm mozilla-inbound opt test mochitest-9 on 2013-07-01 11:01:39 PDT for push 87b5a0591aff slave: tst-linux64-ec2-110 11:55:12 INFO - 28587 INFO TEST-PASS | /tests/layout/style/test/test_property_database.html | 'top' listed in gCSSProperties 11:55:12 INFO - 28588 INFO TEST-PASS | /tests/layout/style/test/test_property_database.html | 'top' listed as CSS_TYPE_LONGHAND 11:55:12 INFO - 28589 INFO TEST-PASS | /tests/layout/style/test/test_property_database.html | 'top' listed with correct DOM property name 11:55:12 INFO - 28590 INFO TEST-PASS | /tests/layout/style/test/test_property_database.html | 'transition-delay' listed in gCSSProperties 11:55:12 INFO - 28591 INFO TEST-PASS | /tests/layout/style/test/test_property_database.html | 'transition-delay' listed as CSS_TYPE_LONGHAND 11:55:12 INFO - 28592 INFO TEST-PASS | /tests/layout/style/test/test_property_database.html | 'transition-delay' listed with correct DOM property name 11:55:12 WARNING - TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_property_database.html | application timed out after 330 seconds with no output 11:55:12 INFO - INFO | automation.py | Application ran for: 0:50:33.182998 11:55:12 INFO - INFO | zombiecheck | Reading PID log: /tmp/tmpwYM3Fypidlog 11:56:17 INFO - checking for crashes in '/data/local/tests/profile/minidumps' 11:56:17 INFO - WARNING | leakcheck | refcount logging is off, so leaks can't be detected! 11:56:17 INFO - INFO | runtests.py | Running tests: end. 11:57:09 ERROR - Return code: 1
Flags: needinfo?(dbaron)
This is among the smallest tests that use property_database.js, so if this one can't run then we've got much bigger problems. I think if we can't run this fast enough then we need to increase timeouts or look into clock consistency issues. (I'm more suspicious of the latter, actually.)
Flags: needinfo?(dbaron)
Closing inactive keywords:intermittent-failure bugs where the TBPLbot has previously commented and the test isn't marked as disabled; filter on orange-cleanup-201401.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.