Closed
Bug 1431859
Opened 6 years ago
Closed 6 years ago
update taskcluster-treeherder to use queue.task or remove scheduler support altogether
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bstack, Assigned: dustin)
References
Details
It appears the only place it is used is [0]. I'm not sure how necessary this is now. [0]https://github.com/taskcluster/taskcluster-treeherder/blob/master/src/handler.js#L331-L347
Assignee | ||
Comment 1•6 years ago
|
||
This is looking at the *reruns*, which the scheduler implements side-by-side with *retries* by re-running tasks when they fail. So this handles (by ignoring) the case where a task fails but we expect the scheduler to re-run it So changing this will cause such "rerun" jobs to appear as failed (red), rather than retried (purple, I think). Johan, am I right in surmising that it wouldn't be the end of the world for releasetasks to display such red jobs? It's just a display change. BTW, the major user of task-graph-scheduler is now tc-vcs. That doesn't report to treeherder, so no risk there.
Flags: needinfo?(jlorenzo)
Assignee | ||
Comment 2•6 years ago
|
||
https://github.com/taskcluster/taskcluster-treeherder/pull/45
Comment 3•6 years ago
|
||
I didn't find anywhere we still use task-graph-scheduler. Mihai pointed out releasetasks stopped its use in bug 1259627. Then, let's remove these lines!
Depends on: 1259627
Flags: needinfo?(jlorenzo)
Assignee | ||
Comment 4•6 years ago
|
||
Oh, right, how could I forget?!
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Blocks: tc-stability
Updated•5 years ago
|
Component: Integration → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•