1641283 - Improve logging around optimization

Status: RESOLVED FIXED

(Firefox Build System :: Task Configuration, task)

Description

[Andrew Halberstadt [:ahal]]

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.

Comment 1

[Andrew Halberstadt [:ahal]]

Attachment: Bug 1641283 - [taskgraph] Upload bugbug push schedules API data to an artifact rather than the log, r?marco

Comment 2

[Andrew Halberstadt [:ahal]]

Attachment: Bug 1641283 - [taskgraph.optimize] Increase debug logging of optimization phase, r?tomprince

For each task, this sheds a bit of light on why it was removed or kept.

Comment 3

[Andrew Halberstadt [:ahal]]

There are some logs we could add in the replace phase in this gist as well:
https://gist.github.com/catlee/3fa9e365a5e8da4e37dd5c7bd5fb6bb9

Comment 4

[Pulsebot]

Pushed by [e-mail]:
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

[Cristina Coroiu [:ccoroiu]]

https://hg.mozilla.org/mozilla-central/rev/f177373e8442
https://hg.mozilla.org/mozilla-central/rev/ed816ec219a2