Closed Bug 1333041 Opened 8 years ago Closed 8 years ago

graph2 tasks are scheduled in graph1 as well for release promotion ESR releases

Categories

(Release Engineering :: Release Automation, defect, P4)

Product:
Release Engineering
Component:
Release Automation
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: mtabara, Assigned: mtabara)

Details

Not sure if this is expected or not, am filing this bug to follow-up whenever I find a minute. As https://tools.taskcluster.net/task-group-inspector/#/3E6x-sNrTseHwaiYqkBkxg/ shows, the graph2 corresponding tasks are also scheduled for graph1. They eventuall die with exceptions due to 5-days time lime in Taskcluster but it'd be worth digging as to why this happens. We don't have this scenario for the mozilla-release so my first guess is that we might have forgotten some variables to set in releasetasks. Will investigate this, assigning this bug to me.
IIRC the idea was to have them in graph1 in case we release earlier than 5 days (dot releases). But it'd be probably more consistent to have them only in graph2.
Component: General Automation → Release Automation
QA Contact: catlee → rail
Priority: -- → P4
Let's leave them in both esr graphs. It doesn't hurt and worse case in this case is that we have 4-5 tasks that die with "Exception" timed-out after 5 days. Once releasetasks is in tree, this won't be a problem anyway so let's not stall useless bugs.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.