Closed Bug 1548749 Opened 6 years ago Closed 5 years ago

Firefox 67.0b16 build1 didn't cancel

Categories

(Release Engineering :: Applications: Shipit, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: nthomas, Unassigned)

Details

[removed deved and fennec from this irc log]
10:58 <taskcluster> sheriffduty: ciduty: releaseduty: New release (firefox 67.0b16 build1) was just created.
11:21 <taskcluster> sheriffduty: ciduty: releaseduty: Phase promote_firefox was just scheduled for release firefox 67.0b16 build1 - (https://tools.taskcluster.net/groups/SCCVmIt2T1WBRcnPo_bXPQ)
11:26 <pascalc> oh, I see that the second part of an uplift was not landed and landed after starting the build, I guess I need to do a build2 :(
11:28 <taskcluster> sheriffduty: ciduty: releaseduty: Release firefox 67.0b16 build1 was just canceled.
11:31 <taskcluster> sheriffduty: ciduty: releaseduty: New release (firefox 67.0b16 build2) was just created.
11:32 <taskcluster> sheriffduty: ciduty: releaseduty: Phase promote_firefox was just scheduled for release firefox 67.0b16 build2 - (https://tools.taskcluster.net/groups/Z5zSAZyRR_CwPORbflyG1g)

There's no cAll for graph SCCVmIt2T1WBRcnPo_bXPQ, so I'm guessing something went wrong in the ship-it backend sending one. Eventually we had update verify failures for build1 as Balrog was offering build2.

We haven't seen this in a while and I believe Mitch had a similar bug that he resolved so I'm going to mark this as works-for-me for now.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in before you can comment on or make changes to this bug.