Closed Bug 1243755 Opened 4 years ago Closed 4 years ago

Consider bumping max deadline to now + 10d

Categories

(Taskcluster :: Services, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rail, Unassigned)

References

Details

When I try to schedule a task with deadline set to date which is more than 5 days in the future I get a 500.

Some release promotion tasks have to wait several days (in case of release it's about 8 days) before we can execute them. Extending the graph afterwards is a bit painful.

10:20 <&jonasfj> we could but it'a a non trivial thing
10:21 <&jonasfj> basically there is a message in an azure queue that becomes visible when deadline is reached.... hence the max time
10:22 <&jonasfj> if we wanted longer max time.. we would have to resubmit that task when received... ie. basically kick it forward every time we see it for 14 days
10:22 <&jonasfj> so we could... we could also change how we resolve deadline issues... but it has to be an issue first
10:23 <rail> that task is a part of a graph with other tasks requiring it...
10:23 <&jonasfj> note: future graphs wont have a deadline... only task
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Component: Queue → Services
You need to log in before you can comment on or make changes to this bug.