Intermittent failure in test_tmpl_wherenosubject.xul | correct number of logged messages - got 3, expected 1

RESOLVED FIXED

Status

()

defect
RESOLVED FIXED
9 years ago
7 years ago

People

(Reporter: mossop, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fixed by bug 612255])

First seen on http://hg.mozilla.org/mozilla-central/rev/c85961497ae9 but basically no way that could have caused it.

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1289600309.1289602792.29303.gz
Rev3 Fedora 12 mozilla-central debug test mochitest-other on 2010/11/12 14:18:29
s: talos-r3-fed-008
1168 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/content/xul/templates/tests/chrome/test_tmpl_wherenosubject.xul | correct number of logged messages - got 3, expected 1
1170 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/content/xul/templates/tests/chrome/test_tmpl_wherenosubject.xul | logged message 2 - got "[JavaScript Error: \"this._timer is null\" {file: \"jar:file:///home/cltbld/talos-slave/mozilla-central_fedora-debug_test-mochitest-other/build/firefox/omni.jar!/components/nsPlacesDBFlush.js\" line: 161}]", expected undefined
1171 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/content/xul/templates/tests/chrome/test_tmpl_wherenosubject.xul | logged message 3 - got "[JavaScript Error: \"this._timer is null\" {file: \"jar:file:///home/cltbld/talos-slave/mozilla-central_fedora-debug_test-mochitest-other/build/firefox/omni.jar!/components/nsPlacesDBFlush.js\" line: 161}]", expected undefined
This isn't actually an XUL templates problem per-say.  The tests expect certain error messages in the console and complain if the correct number is not there.  The extra error message in this case are to do with places timers, though, so this is more sdwilsh's domain I expect.
Comment hidden (Legacy TBPL/Treeherder Robot)
Since nsPlacesDBFlush observes both history and bookmarks it is possible it will get 2 nested onBeginUpdateBatch and onEndUpdateBatch, it should ignore the duplicate calls.
I've filed bug 612255 on that.
Depends on: 612255
should be fixed by fixing the underlying bug
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Whiteboard: [orange] → [orange][fixed by bug 612255]
Whiteboard: [orange][fixed by bug 612255] → [fixed by bug 612255]
You need to log in before you can comment on or make changes to this bug.