Manifestparser generating tons of log spam in `mach taskgraph`
Categories
(Testing :: Mozbase, defect)
Tracking
(firefox-esr102 unaffected, firefox-esr115 unaffected, firefox115 unaffected, firefox116 unaffected, firefox117 fixed, firefox118 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox-esr115 | --- | unaffected |
| firefox115 | --- | unaffected |
| firefox116 | --- | unaffected |
| firefox117 | --- | fixed |
| firefox118 | --- | fixed |
People
(Reporter: ahal, Assigned: tmarble)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
STR:
./mach taskgraph full --target-kind test
Result:
A ton of logs are generated from manifestparser. To an extent that task generation takes noticeably longer just due to all the printing that is happening.
Expected:
Manifestparser does not emit any logs.
I suspect this is a regression from bug 1779473 which had some logging related changes.
| Reporter | ||
Comment 1•2 years ago
|
||
This will likely make Decision tasks slower as well.
Tom, do you think we could revert just the logging portions of your patch?
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1779473
| Reporter | ||
Comment 3•2 years ago
|
||
Here's a recent Decision task log:
https://firefoxci.taskcluster-artifacts.net/EBAhmN88RcOHHPbWb1RuGw/0/public/logs/live_backing.log
Which is mostly just manifestparser log spam.
| Assignee | ||
Comment 4•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Comment 5•2 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #1)
This will likely make Decision tasks slower as well.
Tom, do you think we could revert just the logging portions of your patch?
Yes, in this patch I have lowered the logging level from INFO to DEBUG.
Comment 6•2 years ago
|
||
Set release status flags based on info from the regressing bug 1779473
Comment 8•2 years ago
|
||
| bugherder | ||
Comment 9•2 years ago
|
||
The patch landed in nightly and beta is affected.
:tmarble, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox117towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 10•2 years ago
|
||
I do not think this requires an uplift (I could not change status-firefox-117).
| Reporter | ||
Comment 11•2 years ago
|
||
I think we might as well uplift. The extra logs make debugging things annoying.
| Reporter | ||
Comment 12•2 years ago
|
||
Comment on attachment 9346405 [details]
Bug 1846052 - Reduce manifestparser logging level to DEBUG r=ahal
Beta/Release Uplift Approval Request
- User impact if declined: Decision task logs will be very large and difficult to debug
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky):
- String changes made/needed:
- Is Android affected?: No
Comment 13•2 years ago
|
||
Comment on attachment 9346405 [details]
Bug 1846052 - Reduce manifestparser logging level to DEBUG r=ahal
Approved for 117.0b3.
Comment 14•2 years ago
|
||
| uplift | ||
Updated•2 years ago
|
Description
•