Closed
Bug 1798926
Opened 2 years ago
Closed 2 years ago
`fetch-arcanist` task points at a resource that no longer exists
Categories
(Developer Infrastructure :: Mach Vendor & Updatebot, task)
Developer Infrastructure
Mach Vendor & Updatebot
Tracking
(firefox108 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: ahal, Assigned: jewilde)
References
(Blocks 1 open bug, Regression)
Details
Attachments
(2 files)
I rebuilt cached tasks on mozilla-central (for a Chain of Trust key rotation), and got a failure in the fetch-arcanist
task. It looks like the resource it points at is now a 404:
https://github.com/phacility/arcanist.git/archive/a028291f8e5e79b6446ad67ed8b0be9c5ec8f029.tar.gz
We'll likely need to host this somewhere ourselves going forward.
Reporter | ||
Comment 1•2 years ago
|
||
Though looks like this task is only depended on by the updatebot-cron-win
task, which doesn't appear to ever get scheduled. So maybe it's ok to leave this busted.
Tom, how do you think we should proceed (or not proceed) here?
Flags: needinfo?(tom)
Comment 2•2 years ago
|
||
We can leave it busted for now, although I hope to schedule that task in the future and will need to fix it then.
Blocks: 1738302
Flags: needinfo?(tom)
Comment hidden (Intermittent Failures Robot) |
Updated•2 years ago
|
Assignee: nobody → tom
Component: Task Configuration → Mach Vendor & Updatebot
Product: Firefox Build System → Developer Infrastructure
Assignee | ||
Updated•2 years ago
|
Assignee: tom → jewilde
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Attachment #9302277 -
Attachment filename: file_1798926.txt → phabricator-D161438-url.txt
Assignee | ||
Comment 5•2 years ago
|
||
Pushed by jewilde@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e699b17ef239
Fix resource link for 'fetch-arcanist' task; r=glandium
Comment 7•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•