Closed Bug 1846052 Opened 2 years ago Closed 2 years ago

Manifestparser generating tons of log spam in `mach taskgraph`

Categories

(Testing :: Mozbase, defect)

Default
defect

Tracking

(firefox-esr102 unaffected, firefox-esr115 unaffected, firefox115 unaffected, firefox116 unaffected, firefox117 fixed, firefox118 fixed)

RESOLVED FIXED
118 Branch
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)

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.

This will likely make Decision tasks slower as well.

Tom, do you think we could revert just the logging portions of your patch?

Flags: needinfo?(tmarble)

Set release status flags based on info from the regressing bug 1779473

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: nobody → tmarble
Status: NEW → ASSIGNED

(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.

https://phabricator.services.mozilla.com/D184892

Flags: needinfo?(tmarble)

Set release status flags based on info from the regressing bug 1779473

Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/80892e88c552 Reduce manifestparser logging level to DEBUG r=ahal
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch

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-firefox117 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(tmarble)

I do not think this requires an uplift (I could not change status-firefox-117).

Flags: needinfo?(tmarble)

I think we might as well uplift. The extra logs make debugging things annoying.

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
Attachment #9346405 - Flags: approval-mozilla-beta?

Comment on attachment 9346405 [details]
Bug 1846052 - Reduce manifestparser logging level to DEBUG r=ahal

Approved for 117.0b3.

Attachment #9346405 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: