Windows builds busted on 2019-03-13: HTTPError: 404 Client Error: Not Found for url: https://queue.taskcluster.net/v1/task/UOcjKewPTku96r--36Sz0g/artifacts/public/chain-of-trust.json
Categories
(Thunderbird :: Build Config, defect)
Tracking
(Not tracked)
People
(Reporter: jorgk-bmo, Unassigned)
Details
HTTPError: 404 Client Error: Not Found for url: https://queue.taskcluster.net/v1/task/UOcjKewPTku96r--36Sz0g/artifacts/public/chain-of-trust.json
Log says:
https://taskcluster-artifacts.net/HqrR2l7HSlWLqZDtlO2rAw/0/public/logs/live_backing.log
08:12:13 INFO - If filing a bug, please include the full output of mach, including this error
08:12:13 INFO - message.
08:12:13 INFO - The details of the failure are as follows:
08:12:13 INFO - HTTPError: 404 Client Error: Not Found for url: https://queue.taskcluster.net/v1/task/UOcjKewPTku96r--36Sz0g/artifacts/public/chain-of-trust.json
08:12:13 INFO - File "z:\build\build\src\python/mozbuild/mozbuild/mach_commands.py", line 1486, in artifact_toolchain
08:12:13 INFO - record = ArtifactRecord(task_id, name)
08:12:13 INFO - File "z:\build\build\src\python/mozbuild/mozbuild/mach_commands.py", line 1395, in init
08:12:13 INFO - cot.raise_for_status()
08:12:13 INFO - File "z:\build\build\src\third_party/python/requests\requests\models.py", line 840, in raise_for_status
08:12:13 INFO - raise HTTPError(http_error_msg, response=self)
08:12:13 ERROR - Return code: 1
08:12:13 ERROR - 1 not in success codes: [0]
Regression range:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1994e1ce54af&tochange=9067457d7dcf
Looks like
4768e2c08459 Aki Sasaki — Bug 1534506 - download chain-of-trust.json instead of chainOfTrust.json.asc r=tomprince
https://hg.mozilla.org/mozilla-central/rev/4768e2c08459
Sadly Rob isn't available right no, so Aki or Tom, could you please lend a hand.
Comment 1•5 years ago
|
||
Hm, we probably have to rebuild toolchains and docker images for comm-central.
I'll see if I can figure that out.
Comment 2•5 years ago
|
||
In theory I rebuilt all the toolchains and docker images for comm-central in this push. Once those tasks finish, the next push will hopefully not hit the above error in comment 0.
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Those are rebuilt. In theory the next push shouldn't hit these errors.
Updated•5 years ago
|
Description
•