Closed
Bug 1641283
Opened 4 years ago
Closed 4 years ago
Improve logging around optimization
Categories
(Firefox Build System :: Task Configuration, task)
Firefox Build System
Task Configuration
Tracking
(firefox78 fixed)
RESOLVED
FIXED
mozilla78
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Currently it's very hard to tell why a task was run. Does it have dependents? Was it optimized? If so by which ones?
I'd like to beef up our logging in this area so we can more easily see exactly why any given task was or was not optimized. Maybe as part of a new artifact if it's too verbose.
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
For each task, this sheds a bit of light on why it was removed or kept.
|
|
Assignee | |
Comment 3•4 years ago
|
||
There are some logs we could add in the replace phase in this gist as well:
https://gist.github.com/catlee/3fa9e365a5e8da4e37dd5c7bd5fb6bb9
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f177373e8442 [taskgraph] Upload bugbug push schedules API data to an artifact rather than the log, r=marco https://hg.mozilla.org/integration/autoland/rev/ed816ec219a2 [taskgraph.optimize] Increase debug logging of optimization phase, r=tomprince
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/f177373e8442
https://hg.mozilla.org/mozilla-central/rev/ed816ec219a2
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•