Closed
Bug 1335404
Opened 9 years ago
Closed 9 years ago
Task 3 hours past deadline, yet still pending rather than deadline-exceeded
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: pmoore, Unassigned)
Details
Task https://tools.taskcluster.net/task-inspector/#NcLFZyikQOeU6CySktaPKg/ exceeded its deadline 3 hours ago, but still has state "pending".
This could either be a delay or breakage to the task expiry process in the Queue. Hopefully just an abnormal delay.
Comment 1•9 years ago
|
||
And, critically, it can't be cancelled in this state. Perhaps the cancel operation should mark the task "deadline-exceeded" when it finds it to be past its deadline, rather than returning an error.
| Reporter | ||
Comment 2•9 years ago
|
||
6 hours later now, still not resolved. Last queue deployment was 7 days ago: https://dashboard.heroku.com/apps/queue-taskcluster-net/activity
Comment 4•9 years ago
|
||
Prolonged expiration is known to happen from time to time...
I'll search through logs. But it could be something gets dropped in case of an error that isn't handled right.
We've seen this happen a few time before, so maybe we have a bug.
We should probably scan all tasks to see how many of these are sitting around.
Afaik it's not a common issue.
Flags: needinfo?(jopsen)
| Reporter | ||
Comment 5•9 years ago
|
||
It is resolved now - Jonas did you manually resolve, or did it get resolved by itself? If so, we can probably close this bug.
Flags: needinfo?(jopsen)
Comment 6•9 years ago
|
||
I didn't manually do anything... So maybe the message just got seriously delayed. Well, that's good news.
Thanks for checking up on this.
Flags: needinfo?(jopsen)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•7 years ago
|
Component: Queue → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•