Bug: (meta)  mochitest errors and warnings from FULL DEBUG version of TB.
Status: NEW
Priority: --
Created: 2020-05-15 05:37:02+00:00
Resolved: 2024-10-28 22:36:14+00:00

Most directly related bug is:
bug 303545	[Meta] Javascript strict warnings and errors (Thunderbird)
Maybe also
bug 998697 thunderbird termination errors/warnings [meta]

Hi, mochitest is here to stay for TB. |make mozmill| is gone since December 2019.

I had tough time to figure out converting my script to summarize the errors/warnings in the log spewed by mochitest and xpcshell-test (I try to handle them both with a single script, but now that mochitest has changed the output format pretty much, I need to tinker with the script for a while.)

Now that I have been able to create a somewhat sanitized output (still not so greatly simplified or tidied up) , I am uploading the excerpt from it.

The reason I wanted to upload this is that I think we really ought to handle a few legitimate errors seriously. See the following.

```
  113:  JavaScript error: chrome://messenger/content/customizableui/panelUI.js, line 1346: TypeError: can't access property "firstChild", container is undefined
   20:  JavaScript warning: resource://gre/modules/Troubleshoot.jsm, line 626: WebGL context was lost.
   17:  JavaScript error: chrome://openpgp/content/ui/enigmailMsgComposeOverlay.js, line 483: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgMessageService.messageURIToMsgHdr]
    7:  JavaScript error: resource:///modules/activity/alertHook.jsm, line 49: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIMsgMailNewsUrl.server]
    4:  JavaScript error: resource://testing-common/BrowserTestUtilsChild.jsm, line 267: TypeError: can't access property "href", aEvent.target.location is undefined
    3:  JavaScript error: chrome://messenger/content/messengercompose/MsgComposeCommands.js, line 5257: TypeError: can't access property "key", gCurrentIdentity is null
    2:  JavaScript error: chrome://openpgp/content/ui/enigmailMsgComposeOverlay.js, line 483: NS_ERROR_FACTORY_NOT_REGISTERED: Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIMessenger.messageServiceFromURI]
    2:  JavaScript error: chrome://messenger/content/folderDisplay.js, line 1930: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgDBView.doCommand]
    1:  JavaScript error: resource://services-settings/IDBHelpers.jsm, line 24: Error: IndexedDB: security-state/cert-revocations list() IndexedDB:  execute() The application is shutting down
    1:  JavaScript error: resource://gre/modules/LoginHelper.jsm, line 1192: NS_ERROR_FAILURE: This login already exists.
    1:  JavaScript error: resource://gre/modules/IMIncomingServer.jsm, line 165: TypeError: can't access property "setBool", this.imAccount is null
    1:  JavaScript error: resource:///modules/imXPCOMUtils.jsm, line 272: TypeError: can't access property "values", this._items is undefined
    1:  JavaScript error: resource:///modules/OTRUI.jsm, line 229: NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript Error: "can't access property "values", this._items is undefined" {file: "resource:///modules/imXPCOMUtils.jsm" line: 272}]'[JavaScript Error: "can't access property "values", this._items is undefined" {file: "resource:///modules/imXPCOMUtils.jsm" line: 272}]' when calling method: [nsISimpleEnumerator::iterator]
    1:  JavaScript error: resource:///modules/DBViewWrapper.jsm, line 1113: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgDBView.open]
    1:  JavaScript error: resource:///modules/AddrBookCard.jsm, line 196: NS_ERROR_NOT_AVAILABLE:
    1:  JavaScript error: chrome://mochitests/content/browser/comm/mail/test/browser/notification/browser_notification.js, line 60: NS_ERROR_FAILURE:

```

Without fixing these, the tests are not supposed to perform the expected testing since Javascript tests end prematurely (I think).
Some errors may be "expected" type, but I am not sure. But, if so, the particular test in question should print out "such and such errors are expected from this test. Please ignore them." for long-term maintenance reasons.

The number at the beginning of the following lines is the number of occurrences of the error.

TIA