Closed Bug 1296150 Opened 4 years ago Closed 4 years ago
SM-tc jobs on Beta permafailing due to "Error: cannot GET /Developer
Services/Historical VCSbuild/tooltool .git/info/refs?service=git-upload-pack (404)" errors
Appears to only affect Beta. Aurora has recent green runs. https://public-artifacts.taskcluster.net/dUxAa3LHS1WuKYMTWZXVMw/0/public/logs/live_backing.log
This is a consequence of HTTP redirecting git.mozilla.org as of ~9 hours ago in bug 1290260 (in preparation for its decom). I guess we didn't realize we had Firefox automation still connecting to git.mozilla.org. If beta is impacted, presumably release and esr are impacted. That means there are release implications. Technically these are tier-1 jobs. But according to RyanVM they "probably" don't block release since we still have buildbot SM automation running. If they do block release, we either need a workaround ASAP or to revert the change in bug 1290260.
Severity: normal → blocker
Depends on: 1290260
Priority: -- → P1
I guess the git.mozilla.org landed more than 9 hours ago. Relative timestamps are hard.
AFAICT, no SM-tc jobs run on m-r or esr45.
(In reply to Ryan VanderMeulen [:RyanVM] from comment #4) > AFAICT, no SM-tc jobs run on m-r or esr45. Excellent. That makes this a "someone needs to fix it now" problem to "it can probably wait several hours" problem.
Commits we may want to cherry pick: 2ffda4181e7f (bug 1295900) - currently only on autoland 8e93f47555f5 (bug 1290685) 13fa96518284 (bug 1277957) Of those, the last one is the one that will unbust the SM tasks. It can't be grafted easily though since paths were renamed.
Depends on: 1277957
Comment on attachment 8782219 [details] Bug 1296150 - Obtain tooltool from github.com; https://reviewboard.mozilla.org/r/72426/#review70036
Attachment #8782219 - Flags: review?(ryanvm) → review+
Had to push one more follow-up fix, but things are green now. https://hg.mozilla.org/releases/mozilla-beta/rev/ffe315faba1726473b709697314c13e2da071a62
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.