Closed Bug 718263 Opened 8 years ago Closed 7 years ago

Intermittent failure in test_places/queries/test_tags.js | 3 == 2

Categories

(Toolkit :: Places, defect)

x86
Linux
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Ms2ger, Assigned: mak)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=8557786&tree=Firefox
Rev3 Fedora 12 mozilla-central pgo test xpcshell on 2012-01-14 18:52:55 PST for push 21c84409902e
s: talos-r3-fed-060

TEST-UNEXPECTED-FAIL | /home/cltbld/talos-slave/test/build/xpcshell/tests/toolkit/components/places/tests/queries/test_tags.js | test failed (with xpcshell return code: 0), see following log:
TEST-UNEXPECTED-FAIL | /home/cltbld/talos-slave/test/build/xpcshell/tests/toolkit/components/places/tests/queries/test_tags.js | 3 == 2 - See following stack:
TEST-UNEXPECTED-FAIL | /home/cltbld/talos-slave/test/build/xpcshell/head.js | 2147500036 - See following stack:
On the Thunderbird boxes this is a near-permanent failure on Windows on trunk - seems like bug 559279 has got worse again?

TEST-UNEXPECTED-FAIL | e:/buildbot/comm-central-win32-opt-unittest-xpcshell/build/xpcshell/tests/toolkit/components/places/tests/queries/test_tags.js | 3 == 2 - See following stack:
JS frame :: e:\buildbot\comm-central-win32-opt-unittest-xpcshell\build\xpcshell\head.js :: do_throw :: line 462
JS frame :: e:\buildbot\comm-central-win32-opt-unittest-xpcshell\build\xpcshell\head.js :: _do_check_eq :: line 556
JS frame :: e:\buildbot\comm-central-win32-opt-unittest-xpcshell\build\xpcshell\head.js :: do_check_eq :: line 577
JS frame :: e:/buildbot/comm-central-win32-opt-unittest-xpcshell/build/xpcshell/tests/toolkit/components/places/tests/queries/test_tags.js :: setsAreEqual :: line 811
JS frame :: e:/buildbot/comm-central-win32-opt-unittest-xpcshell/build/xpcshell/tests/toolkit/components/places/tests/queries/test_tags.js :: queryResultsAre :: line 788
JS frame :: e:/buildbot/comm-central-win32-opt-unittest-xpcshell/build/xpcshell/tests/toolkit/components/places/tests/queries/test_tags.js :: ORed_queries :: line 565
JS frame :: e:\buildbot\comm-central-win32-opt-unittest-xpcshell\build\xpcshell\head.js :: _run_next_test :: line 882
JS frame :: e:\buildbot\comm-central-win32-opt-unittest-xpcshell\build\xpcshell\head.js :: <TOP_LEVEL> :: line 429
(In reply to Mark Banner (:standard8) from comment #1)
> On the Thunderbird boxes this is a near-permanent failure on Windows on
> trunk - seems like bug 559279 has got worse again?

when did this "near-permaorange" started?
Assignee: nobody → mak77
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: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.