592585 - libeditor is spamming the test logs with "WARNING: NS_ENSURE_TRUE(...)" failures

Status: RESOLVED INVALID

(Core :: DOM: Editor, defect)

Description

[Serge Gautherie (:sgautherie)]

Examples:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1280795505.1280798850.12367.gz
WINNT 5.2 mozilla-central debug test mochitests-3/5 on 2010/08/02 17:31:45
{
WARNING: NS_ENSURE_TRUE(mDoneSetup) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/composer/src/nsEditingSession.cpp, line 561
7984 ERROR TEST-UNEXPECTED-FAIL | /tests/editor/libeditor/html/tests/test_bug484181.html | Correct number of misspellings and words. - got 0, expected 2
7985 ERROR TEST-UNEXPECTED-FAIL | /tests/editor/libeditor/html/tests/test_bug484181.html | All misspellings before editing are accounted for. - got false, expected true
WARNING: NS_ENSURE_TRUE(mListenerEnabled) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsHTMLEditRules.cpp, line 8429
WARNING: NS_ENSURE_TRUE(elem) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsHTMLEditUtils.cpp, line 396
WARNING: NS_ENSURE_TRUE(elem) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsHTMLEditUtils.cpp, line 396
WARNING: NS_ENSURE_TRUE(mLastNBSPNode) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsWSRunObject.cpp, line 663
WARNING: NS_ENSURE_TRUE(*outIsEmptyNode) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsHTMLEditor.cpp, line 5095
...
}

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1283306532.1283310521.11607.gz&fulltext=1
Linux comm-central-trunk debug test mochitests-3/5 on 2010/08/31 19:02:12

NB: The ("unrelated") test failure itsef is bug 574880.

Comment 1

[(no longer active)]

Most of those logs are useful for debugging purposes.  If you know or any specific ones which really spam the logs (i.e.,  generate tens of consecutive lines for the same test all the time), feel free to file specific bugs about them, and I'll be happy to patch them.