Closed Bug 1180726 Opened 10 years ago Closed 9 years ago

Retrigger from taskcluster job in treeherder don't work

Categories

(Taskcluster :: General, defect)

Product:
Taskcluster
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cbook, Unassigned)

Details

retriggering taskcluster jobs from treeherder as example a mulet test does not work. Seems this is either a taskcluster or treeherder ? regression Retrigger via task inspector works
Greg, any news here? This should probably be a tree closing issue.
Flags: needinfo?(garndt)
Still looking into the issue, so far haven't seen any reason why mozilla-taskcluster is not retriggering these jobs. It appears that it consume the pulse message because right afterwards there are bits in the logs showing it querying the queue for the task, but then does nothing after that. I'll keep the ni? here as I am still looking into this. I believe, while not ideal workflow at all, that tasks can be rerun by going to the task inspector.
It appears that this was a multiple part issue that was resolved by deploying a new redis backend for our mozilla-taskcluster and mozilla-taskcluster-staging services. I have a support ticket open with redisCloud to find out why we were having issues with that redis instance, but for now retriggers are working with this bandaid solution.
Flags: needinfo?(garndt)
Component: TaskCluster → General
Product: Testing → Taskcluster
Old Heroku-related issue that was resolved.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.