Closed
Bug 1915569
Opened 1 year ago
Closed 1 year ago
Regression on console.log in workers
Categories
(Core :: Machine Learning: General, defect)
Core
Machine Learning: General
Tracking
()
RESOLVED
FIXED
132 Branch
| Tracking | Status | |
|---|---|---|
| firefox132 | --- | fixed |
People
(Reporter: tarek, Assigned: gregtatum)
Details
Attachments
(1 file)
Looks like we don't get the console logs anymore with
ChromeUtils.defineLazyGetter(lazy, "console", () => {
return console.createInstance({
maxLogLevel: _logLevel, // we can't use maxLogLevelPref in workers.
prefix: "ML:ONNXPipeline",
});
});
in workers. This seems to be a regression on the latest changes done in console
| Reporter | ||
Comment 1•1 year ago
|
||
To reproduce:
- run nightly with
MOZ_ALLOW_EXTERNAL_ML_HUB=1 - set
browser.ml.logLeveltoDebug,browser.ml.enabletotrue - open a browser multi-process console
- open about:inference. Run an inference.
The console should be filled with 20+ messages from ML:
| Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → gtatum
Status: NEW → ASSIGNED
Pushed by tziade@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d79ae5e317d6
Fix logging in ONNXPipeline.mjs; r=tarek
Comment 4•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox132:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•