Closed
Bug 1503195
Opened 7 years ago
Closed 7 years ago
Mention deadline for build_metrics regressions
Categories
(Tree Management :: Perfherder, enhancement)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: igoldan, Assigned: igoldan)
References
Details
Attachments
(1 file)
The templated message for build_metrics regressions misses the text:
"*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***"
It must be added to avoid developer confusion like it happened here [1].
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1501178#c1
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
is this something we want to do? I don't think backing out build related changes is realistic- please confirm with the build tools team this is desirable?
Flags: needinfo?(igoldan)
| Assignee | ||
Comment 3•7 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #2)
> is this something we want to do? I don't think backing out build related
> changes is realistic- please confirm with the build tools team this is
> desirable?
I thought this procedure applies to all our tests.
:kmoir do you agree on allowing us Perf sheriffs to backout build related changes that caused regressions, but for which the authors didn't respond within 3 business days?
Flags: needinfo?(igoldan) → needinfo?(kmoir)
Comment 4•7 years ago
|
||
IIRC we agreed a few years ago not to back out build_metrics regressions, we would just notify who was responsible for them that they occurred. This was probably never written down...
Comment 5•7 years ago
|
||
I brought up this issue in our team meeting today and they agreed that having it at the same level as the others (3 days) is reasonable as long as they are notified.
Flags: needinfo?(kmoir)
Comment 6•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/bfd784e0fbb68d3a1fba44f287dedeaa95db1ace
Bug 1503195 - Mention deadline for build_metrics regressions (#4210)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•