Task duration and impact in `mach try` push summary.
Categories
(Release Engineering :: General, enhancement)
Tracking
(firefox75 fixed)
| Tracking | Status | |
|---|---|---|
| firefox75 | --- | fixed |
People
(Reporter: sfraser, Assigned: sfraser)
References
Details
Attachments
(1 file)
Following work in Bug 1590410, we should add the task duration and impact estimates to the output produced by push.py, so that it's available regardless of the try method used.
Current patch in progress adds entries such as this before the push lines:
estimates: Added 2 dependencies for a total 4 tasks
estimates: Total cpu time used 0:22:12
estimates: This is in the top 48% of pushes
estimates: Push should take about 0:18:36
estimates: Finish around 2020-01-28 21:39
|
Assignee | |
Comment 1•4 years ago
|
||
Add duration estimates to push summary. Refactored preview script - needed to be moved in order to import module.
|
||
Comment 2•4 years ago
|
||
+1, thanks for filing!
This actually came up in our scheduling session. Multiple developers asked if we could print a cost estimate on push, and were surprised that the feature already exists. This will make it much more visible and not be fuzzy only.
|
|
Assignee | |
Comment 3•4 years ago
|
||
Should we revisit adding the costs themselves or is that still considered sensitive data? It's closely linked to duration, so the timing may be close enough.
Pushed by sfraser@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/30cad1646e4a Refactor try estimates for code re-use. r=ahal
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Description
•