Closed Bug 711870 Opened 8 years ago Closed 7 years ago

Intermittent browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250

Categories

(Firefox :: Bookmarks & History, defect)

11 Branch
x86
Windows XP
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

+++ This bug was initially created as a clone of Bug #711279 +++

https://tbpl.mozilla.org/php/getParsedLog.php?id=8019147&tree=Mozilla-Inbound
Rev3 WINNT 5.1 mozilla-inbound opt test mochitest-other on 2011-12-18 12:49:46 PST for push 8288419ba591

TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Start of test: Bug 475529 - Add button in new folder dialog not default anymore
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | an unexpected uncaught JS exception reported through window.onerror - aNode is null at resource://gre/modules/PlacesUtils.jsm:250
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Console message: [JavaScript Error: "aNode is null" {file: "resource://gre/modules/PlacesUtils.jsm" line: 250}]
TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Console message: [JavaScript Error: "aNode is null" {file: "resource://gre/modules/PlacesUtils.jsm" line: 250}]
TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Console message: [JavaScript Error: "aNode is null" {file: "resource://gre/modules/PlacesUtils.jsm" line: 250}]
TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Console message: [JavaScript Error: "aNode is null" {file: "resource://gre/modules/PlacesUtils.jsm" line: 250}]
TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Console message: [JavaScript Error: "aNode is null" {file: "resource://gre/modules/PlacesUtils.jsm" line: 250}]
TEST-INFO | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Console message: [JavaScript Error: "aNode is null" {file: "resource://gre/modules/PlacesUtils.jsm" line: 250}]
TEST-PASS | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_bookmarksProperties.js | Sidebar tree has been loaded
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.