Closed
Bug 1113779
Opened 10 years ago
Closed 9 years ago
UserCustomizations.jsm spams desktop mochitest test logs
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Gijs, Assigned: fabrice)
References
Details
Attachments
(1 file, 2 obsolete files)
4.73 KB,
patch
|
mccr8
:
review+
mccr8
:
feedback+
|
Details | Diff | Splinter Review |
Random example: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-linux/1419013123/fx-team_ubuntu32_vm_test-mochitest-browser-chrome-1-bm03-tests1-linux32-build253.txt.gz 10:45:44 INFO - -*-*- UserCustomizations (parent): document created: http://tracking.example.org/browser/browser/base/content/test/general/benignPage.html times many thousands. Can we please disable this logging by default, and enable it only in relevant tests? I'm not even entirely sure why this module is shipped on desktop at all, but that is its own issue.
Fabrice, can you suggest a fix here? This generates a huge amount of spam, to the point that it's hard to do printf debugging while running tests. It looks like this code is getting tested on desktop because there's some problem that makes it impossible to run the tests on b2g. Is that right? Could we perhaps only enable the customizations while running the marketplace tests? It looks like the code doesn't allow that right now, but maybe it wouldn't be too hard.
Flags: needinfo?(fabrice)
Assignee | ||
Comment 2•9 years ago
|
||
Bill, I didn't test locally, but it's simple enough and will show debug messages only when running the UserCustomizations.jsm tests.
Assignee: nobody → fabrice
Flags: needinfo?(fabrice)
Attachment #8545707 -
Flags: review?(wmccloskey)
Comment on attachment 8545707 [details] [diff] [review] debug-customizations.patch Review of attachment 8545707 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/apps/UserCustomizations.jsm @@ +36,5 @@ > * } > * ] > */ > > +let debug = Services.prefs.getBoolPref("dom.mozApps.customizations.debug") I don't think this will work. |debug| is assigned once when the module is loaded. The pref will presumably be false then. After that, even if the pref is enabled, debug will continue to refer to the disabled version of the function. I think you have to check the pref every time the function is called or else use a pref observer to modify the value of |debug|.
Attachment #8545707 -
Flags: review?(wmccloskey)
Comment 4•9 years ago
|
||
I got tired of seeing this in my local mochitest runs, so I updated the patch according to Bill's suggestion. It would be nice if other modules could do the same thing (Webapps.jsm comes to mind), but that can be a separate bug. Instead of determining the debugging helper for UserCustomizations.jsm at module import time, register a preference observer so that we can change the debugging helper on the fly.
Attachment #8545707 -
Attachment is obsolete: true
Attachment #8550376 -
Flags: review?(wmccloskey)
I don't think this is quite right. We need to update the value of |debug| in the pref observer. I think we also need to remove the pref observer at shutdown. Fabrice, is it okay to just disable this logging in tests? It doesn't seem worth all the time we're putting into it.
Flags: needinfo?(fabrice)
Comment 6•9 years ago
|
||
About one third of the entire Mochitest 5 log is a single "document created" UserCustomizations line, from a large data URI. If we don't enable it, we should at least truncate what gets printed out a little.
Comment 7•9 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #6) > If we don't enable it This should read _disable it_ of course.
Assignee | ||
Comment 8•9 years ago
|
||
Untested yet, but this patch disables logging in this file by default, and let test opt-in through SpecialPowers.
Attachment #8550376 -
Attachment is obsolete: true
Attachment #8550376 -
Flags: review?(wmccloskey)
Flags: needinfo?(fabrice)
Comment 9•9 years ago
|
||
Comment on attachment 8550513 [details] [diff] [review] usercustom-logs.patch I tested this locally and it fixes the spam. There's still some of the -*-*- Langpacks: getAdditionalLanguages http://example.org/manifest.webapp -*-*- Langpacks: Languages found: ({langs:{}}) stuff but maybe that's unrelated. In any event, that doesn't seem to be per-test.
Attachment #8550513 -
Flags: feedback+
Thanks Fabrice. It looks like the Langpacks stuff comes from Langpacks.jsm. Can we give that one the same treatment?
Comment 11•9 years ago
|
||
Comment on attachment 8550513 [details] [diff] [review] usercustom-logs.patch Review of attachment 8550513 [details] [diff] [review]: ----------------------------------------------------------------- Looks reasonable to me. It seems a bit brittle but I guess it is better than what we have now. ;)
Attachment #8550513 -
Flags: review+
Assignee | ||
Comment 12•9 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/e5a20f32cbef
Comment 14•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/e5a20f32cbef
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•