Closed Bug 604786 Opened 14 years ago Closed 14 years ago

64 bit mac: (permanent orange) TEST-UNEXPECTED-FAIL | test_js_weak_references.js | false == true (from Tracemonkey compartments landing)

Categories

(Core :: XPConnect, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: standard8, Unassigned)

References

Details

(Keywords: intermittent-failure, regression, Whiteboard: [tbtrunkneeds])

I spotted this because we're in the process of setting up 64 bit builders on Thunderbird. However, if you view the hidden builders on the Firefox tree and look for MacOSX Snow Leopard 10.6.2 mozilla-central opt test xpcshell then you'll see it:

http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox&noignore=1

Going back in time, this can be seen to be directly attributable to the tracemonkey compartments landing regression range.

Log:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287029264.1287029901.17684.gz#err0

TEST-UNEXPECTED-FAIL | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | test failed (with xpcshell return code: 0), see following log:
  >>>>>>>
  TEST-INFO | (xpcshell/head.js) | test 1 pending
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 44] true == true
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 45] true == true
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 46] true == true
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 52] true == true
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 53] true == true
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 54] true == true
TEST-PASS | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | [run_test : 62] true == true
TEST-UNEXPECTED-FAIL | /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | false == true - See following stack:
JS frame :: /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/head.js :: do_throw :: line 317
JS frame :: /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/head.js :: do_check_eq :: line 347
JS frame :: /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/head.js :: do_check_true :: line 359
JS frame :: /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js :: run_test :: line 68
JS frame :: /Users/cltbld/talos-slave/mozilla-central_snowleopard_test-xpcshell/build/xpcshell/head.js :: _execute_test :: line 203
JS frame :: -e :: <TOP_LEVEL> :: line 1
TEST-INFO | (xpcshell/head.js) | exiting test

  <<<<<<<
I think this should be blocking as its a test regression on a builder, even if that builder is hidden (I believe the builder should probably be unhidden now, but that's a different issue).
blocking2.0: --- → ?
Whiteboard: [orange] → [orange][tbtrunkneeds]
Blocks: 438871
It appears this may have fixed itself at some stage - it certainly isn't permanent now.
Status: NEW → RESOLVED
blocking2.0: ? → ---
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange][tbtrunkneeds] → [tbtrunkneeds]
You need to log in before you can comment on or make changes to this bug.