Fix warnings "Chrome file doesn't exist head.js" in debug test runs
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
People
(Reporter: tomasz, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141115160330 Steps to reproduce: Run a test with no head.js. Expected results: It seems to be totally useless in the test output. Get rid of it to make the output cleaner.
Updated•10 years ago
|
Comment 1•10 years ago
|
||
What testsuites does this happen in? I *think* this is xpcshell tests, but you haven't said. :-)
Reporter | ||
Comment 2•10 years ago
|
||
mochitest-browser. I saw this while I was working on bug 1080229.
Updated•10 years ago
|
Updated•10 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 3•4 years ago
|
||
Hi,
Thunderbird has transitioned from |make mozmill| test suite to mochitest since December 2019.
Now, I see the following "Chrome file doesn't exist errors" during my local run of mochitest with FULL DEBUG version of TB.
The list is created by my handcrafted log summarizer script.
The number at the beginning of each line is the frequency of occurrences of the warning lines.
If these are useless warnings then why don't we get rid of it?
HOWEVER, there is one case which I think might be worth reporting.
This is the most frequent case of warnings.: The data field of a structure or class was null when it was referenced. Something is really amiss.
162 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/content/messenger/messengercompose/null
The full list:
========================================
Chrome file doesn't exist (checked since Apri 2, 2015)
========================================
162 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/content/messenger/messengercompose/null
48 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/en-US/locale/en-US/global/app-extension-fields.properties
27 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/folder-display/head.js
10 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/account/head.js
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/skin/classic/messenger/messages/mail/Outgoing/NextContext.html
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/skin/classic/messenger/messages/mail/Outgoing/NextContent.html
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/skin/classic/messenger/messages/mail/Outgoing/Context.html
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/skin/classic/messenger/messages/mail/Outgoing/Content.html
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/skin/classic/messenger/messages/mail/Incoming/NextContext.html
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/messenger/skin/classic/messenger/messages/mail/Header.html
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/chrome/browser/content/content.js
7 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/content-policy/head.js
5 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/quick-filter-bar/head.js
5 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/message-window/head.js
5 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/message-header/head.js
5 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/folder-tree-modes/head.js
5 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/attachment/head.js
5 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/calendar/test/browser/views/head.js
4 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/folder-pane/head.js
3 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/tabmail/head.js
3 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/search-window/head.js
3 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/content-tabs/head.js
2 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/utils/head.js
2 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/im/head.js
2 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/addrbook/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/subscribe/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/startup-firstrun/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/smime/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/session-store/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/override-main-menu-collapse/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/notification/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/newmailaccount/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/multiple-identities/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/message-reader/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/keyboard/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/junk-commands/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/instrumentation/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/folder-widget/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/downloads/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/test/browser/cookies/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/components/enterprisepolicies/tests/browser/disable_developer_tools/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/components/enterprisepolicies/tests/browser/disable_app_update/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/mail/base/test/browser/head.js
1 Chrome file doesn't exist: /NEW-SSD/moz-obj-dir/objdir-tb3/_tests/testing/mochitest/browser/comm/calendar/test/browser/invitations/head.js
/NEW-SSD/mozobj-dir/objdir-tb3 is MOZ_OBJ directory for local TB build.
head.js may be a case which we can safely ignore from the original comment of this bugzilla, but what about other cases?
Any guidance on which way to go dig into the true cause of warnings ASIDE from the head.js cases, etc. is appreciated.
Comment 4•4 years ago
|
||
The warning comes from https://searchfox.org/mozilla-central/rev/3262e013550a0db7c1840a78a3878a929801fe40/chrome/nsChromeProtocolHandler.cpp#157
Yes, some of these errors look problematic. The simplest way of figuring out what's causing this is probably to replace it with something like nsTraceRefcnt::WalkTheStack(stderr)
and run a single test that hits some of these errors.
The head.js ones can probably be ignored; it'd require doing some checks at https://searchfox.org/comm-central/rev/b37b719d78f1f67c72c20a18fc96a76b61fe08bb/mozilla/testing/mochitest/browser-test.js#987,989 before trying to load it via a chrome channel - or just hack up an exception for things ending in head.js
in that DEBUG-only chrome protocol code.
Updated•2 years ago
|
Description
•