If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

64-bit win7: TEST-UNEXPECTED-FAIL | C:/talos-slave/mozilla-central_w764_test-xpcshell/build/xpcshell/tests/TestXPC/unit/test_js_weak_references.js | false == true

RESOLVED WORKSFORME

Status

()

Core
XPConnect
RESOLVED WORKSFORME
7 years ago
5 years ago

People

(Reporter: m_kato, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86_64
Windows 7
intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
See http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1281525465.1281526895.20486.gz

Even if xpcshell grows stack size to 2MB to fix stackoverflow by test_encoding_errors.js, this still occurs.
Blocks: 438871
Whiteboard: [orange]
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1284155397.1284159327.23468.gz
Rev3 WINNT 6.1 mozilla-central opt test xpcshell [testfailed]

s: talos-r3-w7-026
TEST-UNEXPECTED-FAIL | c:\talos-slave\mozilla-central_win7_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-UNEXPECTED-FAIL | c:/talos-slave/mozilla-central_win7_test-xpcshell/build/xpcshell/tests/js/src/xpconnect/tests/unit/test_js_weak_references.js | false == true - See following stack:
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
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
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

5 years ago
Keywords: intermittent-failure
(Assignee)

Updated

5 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.