Closed Bug 558497 Opened 14 years ago Closed 11 years ago

Intermittent failure in test_processasync.js | false == true or "value {0} at index {1} should be zero"

Categories

(Testing :: General, defect)

Product:
Testing
Component:
General
Version:
1.9.2 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure) 

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.6/1270857648.1270858081.32203.gz
Linux mozilla-1.9.2 test xpcshell on 2010/04/09 17:00:48
s: moz2-linux-slave09

TEST-PASS | /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/tests/test_necko/test/test_processasync.js | [stop_handleAsyncOrdering : 370] 1310720 == 1310720
TEST-UNEXPECTED-FAIL | /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/tests/test_necko/test/test_processasync.js | false == true - See following stack:
JS frame :: /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/head.js :: do_throw :: line 200
JS frame :: /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/head.js :: do_check_eq :: line 230
JS frame :: /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/head.js :: do_check_true :: line 242
JS frame :: /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/tests/test_necko/test/test_processasync.js :: stop_handleAsyncOrdering :: line 371
JS frame :: /builds/moz2_slave/mozilla-1.9.2-linux-unittest-xpcshell/build/xpcshell/tests/test_necko/test/head_utils.js :: anonymous :: line 426
Pushed http://hg.mozilla.org/mozilla-central/rev/6d68fc7bfe7d to maybe help with diagnosing this -- not sure how much diagnostic info to print out, starting with just the first bogus byte and can narrow after that depending on what we discover...
Summary: Intermittent failure in test_processasync.js | false == true → Intermittent failure in test_processasync.js | false == true or "value {0} at index {1} should be zero"
I hit this on the Firefox 3.6.11 build 3 xpcshell test run for linux

TEST-UNEXPECTED-FAIL | /builds/slave/release-mozilla-1.9.2-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_necko/test/test_processasync.js | false == true - See following stack:
JS frame :: /builds/slave/release-mozilla-1.9.2-linux-opt-unittest-xpcshell/build/xpcshell/head.js :: do_throw :: line 200
JS frame :: /builds/slave/release-mozilla-1.9.2-linux-opt-unittest-xpcshell/build/xpcshell/head.js :: do_check_eq :: line 230
JS frame :: /builds/slave/release-mozilla-1.9.2-linux-opt-unittest-xpcshell/build/xpcshell/head.js :: do_check_true :: line 242
JS frame :: /builds/slave/release-mozilla-1.9.2-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_necko/test/test_processasync.js :: stop_handleAsyncOrdering :: line 371
JS frame :: /builds/slave/release-mozilla-1.9.2-linux-opt-unittest-xpcshell/build/xpcshell/tests/test_necko/test/head_utils.js :: anonymous :: line 426
TEST-INFO | (xpcshell/head.js) | exiting test
TEST-INFO | (xpcshell/head.js) | test 2 pending
>>> stopping listening on port 4444
TEST-INFO | (xpcshell/head.js) | test 2 finished
>>> shutting down server on port 4444
*** no open connections, notifying async from onStopListening
*** _notifyStopped async callback
TEST-INFO | (xpcshell/head.js) | test 1 finished
TEST-INFO | (xpcshell/head.js) | exiting test

  <<<<<<<
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Component: httpd.js → General
You need to log in before you can comment on or make changes to this bug.