Closed
Bug 1402136
Opened 7 years ago
Closed 6 years ago
Integration tool should mark a commit as successful if task retriggers are successful
Categories
(Taskcluster :: Services, enhancement, P5)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1465161
People
(Reporter: kats, Unassigned)
References
Details
Attachments
(1 file)
55.21 KB,
image/png
|
Details |
I pushed a commit to [1]. The .taskcluster.yml file caused the triggering of the taskgroup at [2]. This group has 4 jobs, one of which (the OS X Release tests) failed on the first attempt. This resulted in the commit being marked as failing by the integration tool. I fixed a thing on the worker that caused the failure, and retriggered the task. This time it passed. However, the commit is still marked as failing, but I think it should be updated to be marked as passing. In general it should probably take the status of the most recent run of each task. This would be useful in cases where there are intermittent failures due to $random_flakiness where just retriggering the task is sufficient to clear things up.
(I'm not sure of the exact pieces that are involved here, apologies if this is unclear).
[1] https://github.com/staktrace/webrender/commits/taskcluster-osx
[2] https://tools.taskcluster.net/groups/IT7TFtaCRIqxiCk2atTUBw
Reporter | ||
Comment 1•7 years ago
|
||
The red X on the topmost commit (see screenshot) is what I'm referring to when I mean the commit was marked failing.
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
Priority: -- → P5
Updated•6 years ago
|
Severity: normal → enhancement
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: Github → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•