1635695 - Perma [taskcluster:error] exit status 101 | error: failed to get `goblin` as a dependency of package

Status: RESOLVED FIXED

(Firefox Build System :: Toolchains, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: rgurzau [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=300992179&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/YBj6VlAVRWiUV0s1SPM4bw/runs/0/artifacts/public/logs/live_backing.log

---

[task 2020-05-06T07:49:41.264Z] error: failed to get goblin as a dependency of package symbolic-debuginfo v7.0.0 (https://github.com/getsentry/symbolic/?rev=d951dd683a62d32595cc232e93843bffe5bd6a17#d951dd68)
[task 2020-05-06T07:49:41.264Z] ... which is depended on by dump_syms v0.0.4 (Z:\task_1588750929\fetches\dump_syms)
[task 2020-05-06T07:49:41.264Z]
[task 2020-05-06T07:49:41.264Z] Caused by:
[task 2020-05-06T07:49:41.264Z] failed to load source for dependency goblin
[task 2020-05-06T07:49:41.264Z]
[task 2020-05-06T07:49:41.264Z] Caused by:
[task 2020-05-06T07:49:41.264Z] Unable to update https://github.com/jan-auer/goblin?rev=ee8b997792d37cfb35f8656c028543797425137e#ee8b9977
[task 2020-05-06T07:49:41.264Z]
[task 2020-05-06T07:49:41.264Z] Caused by:
[task 2020-05-06T07:49:41.264Z] revspec 'ee8b997792d37cfb35f8656c028543797425137e' not found; class=Reference (4); code=NotFound (-3)
[fetches 2020-05-06T07:49:41.272Z] removing Z:/task_1588750929/fetches
[fetches 2020-05-06T07:49:41.842Z] finished
[taskcluster 2020-05-06T07:49:41.862Z] Exit Code: 101
[taskcluster 2020-05-06T07:49:41.862Z] User Time: 0s
[taskcluster 2020-05-06T07:49:41.862Z] Kernel Time: 0s
[taskcluster 2020-05-06T07:49:41.862Z] Wall Time: 5m18.2084071s
[taskcluster 2020-05-06T07:49:41.862Z] Result: FAILED
[taskcluster 2020-05-06T07:49:41.862Z] === Task Finished ===
[taskcluster 2020-05-06T07:49:41.862Z] Task Duration: 5m18.2084071s
[taskcluster 2020-05-06T07:49:42.129Z] Uploading artifact public/build/toolchains.json from file public\build\toolchains.json with content encoding "gzip", mime type "application/octet-stream" and expiry 2021-05-06T07:29:29.580Z
[taskcluster 2020-05-06T07:49:42.396Z] Uploading artifact public/logs/certified.log from file generic-worker\certified.log with content encoding "gzip", mime type "text/plain; charset=utf-8" and expiry 2021-05-06T07:29:29.580Z
[taskcluster 2020-05-06T07:49:42.566Z] Uploading artifact public/chain-of-trust.json from file generic-worker\chain-of-trust.json with content encoding "gzip", mime type "text/plain; charset=utf-8" and expiry 2021-05-06T07:29:29.580Z
[taskcluster 2020-05-06T07:49:42.674Z] Uploading artifact public/chain-of-trust.json.sig from file generic-worker\chain-of-trust.json.sig with content encoding "gzip", mime type "application/octet-stream" and expiry 2021-05-06T07:29:29.580Z
[taskcluster 2020-05-06T07:49:43.003Z] Uploading redirect artifact public/logs/live.log to URL https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/YBj6VlAVRWiUV0s1SPM4bw/runs/0/artifacts/public/logs/live_backing.log with mime type "text/plain; charset=utf-8" and expiry 2021-05-06T07:29:29.580Z
[taskcluster:error] exit status 101

Comment 1

[Mike Hommey [:glandium]]

Attachment: Bug 1635695 - Upgrade dump-syms to 0.0.5.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6f68220e32d6
Upgrade dump-syms to 0.0.5. r=calixte

Comment 3

[Mike Hommey [:glandium]]

Comment on attachment 9146087 [details]
Bug 1635695 - Upgrade dump-syms to 0.0.5.

Beta/Release Uplift Approval Request

• User impact if declined: Build failures if the toolchain is ever rebuilt.
• Is this code covered by automated tests?: No
• Has the fix been verified in Nightly?: Yes
• Needs manual test from QE?: No
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Medium
• Why is the change risky/not risky? (and alternatives if risky): This is not part of the shipped Firefox. This is the tool used to dump the debug symbols for Windows builds so that we can process crash reports. One possibility is for the updated tool to miss some symbols or something, making crash reports less useful. This early in the release cycle, we should catch any such problem fairly quickly.
• String changes made/needed:

Comment 4

[Pascal Chevrel:pascalc]

Comment on attachment 9146087 [details]
Bug 1635695 - Upgrade dump-syms to 0.0.5.

Uplift approved for 77.0b3, thanks.

Comment 5

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/6f68220e32d6

Comment 6

[Julien Cristau [:jcristau]]

https://hg.mozilla.org/releases/mozilla-beta/rev/246dd734ffe5

Comment 7

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Backed out from beta for toolchain failures (bug 1635860): https://hg.mozilla.org/releases/mozilla-beta/rev/6e29185107502247b469d2489c2913f7c18c285c

Push with failures: https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&selectedTaskRun=T3dgfnsTTl29sPiLPYFiCw-0&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=246dd734ffe51d466c034eb94b18aae918e05fe4

Comment 8

[Mike Hommey [:glandium]]

So, symbolic 7.3 uses something that wasn't stable yet in rust 1.41. That wasn't the case in 7.2, so we could either revert back to that by patching Cargo.lock, or just hope that we won't need to rebuild dump_syms during the beta cycle and the following release cycle... which I guess might be a good assumption? (I wouldn't take that bet if it were an ESR, though)

Ryan, what do you think?

Comment 9

[Ryan VanderMeulen [:RyanVM]]

TBH, ESR68 is nearing the end of its lifecycle and I'm wondering how likely it is that we'd even need to worry about this there either. But I'm missing some context here - why is this happening only now and affecting all trees?

Comment 10

[Mike Hommey [:glandium]]

It's not affecting ESR68, we've only started using this toolchain recently. It doesn't cause an immediate problem on beta either, only if the toolchain happens to be rebuilt, in which case it will fail because some git commits vanished from github (presumably by some PR branch being removed). AIUI, we sometimes trigger rebuilds of everything including toolchains, which would hit this (but not on esr68). The question is whether this is likely to happen during the lifecycle of 77. There are other things that may trigger toolchains to be rebuilt, but those are not very common, but if they do happen, then we'll hit this bug.

Comment 11

[Ryan VanderMeulen [:RyanVM]]

That seems unlikely enough to not worry about. If we find ourselves in that situation at some point over the next 4 weeks while 77 is on Beta, we can worry about it then.

Comment 12

[Intermittent Failures Robot]

1 failures in 5276 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 1

Platform breakdown:

• toolchains: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1635695&startday=2020-05-04&endday=2020-05-10&tree=all