Could not find artifacts for a toolchain build named `macosx64-minidump-stackwalk`.
Categories
(Firefox Build System :: Bootstrap Configuration, defect, P3)
Tracking
(firefox80 unaffected, firefox81 affected)
Tracking | Status | |
---|---|---|
firefox80 | --- | unaffected |
firefox81 | --- | affected |
People
(Reporter: cpeterson, Assigned: mhentges)
References
(Blocks 1 open bug)
Details
(Keywords: in-triage)
Attachments
(2 files)
I hit the following fix-stacks error when running mach bootstrap:
0:04.97 Setting up artifact fix-stacks.tar.xz
0:04.97 Using artifact from local cache: /Users/chris/.mozbuild/toolchains/5e9f355a22b8afe6-fix-stacks.tar.xz
0:04.98 rm tree: /Users/chris/.mozbuild/fix-stacks
0:04.98 untarring "/Users/chris/.mozbuild/fix-stacks.tar.xz"
0:04.65 Could not find artifacts for a toolchain build named `macosx64-minidump-stackwalk`. Local commits, dirty/stale files, and other changes in your checkout may cause this error. Make sure you are on a fresh, current checkout of mozilla-central. If you are already, you may be able to avoid this error by running `mach clobber python`. Beware that commands like `mach bootstrap` and `mach artifact` are unlikely to work on any versions of the code besides recent revisions of mozilla-central.
I am running macOS 10.15.6 and have an up-to-date checkout of mozilla-central and no objdir.
Likely related to "mach bootstrap fails installing minidump stackwalk" bug 1636797?
Reporter | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Hey :cpeterson, we found out the core issue in that related bug: TASKCLUSTER_ROOT_URL
was set to the old Taskcluster instance.
Is that what's causing your failure?
If not, can you apply this patch (hg import --no-commit debug-artifact.patch
) and paste your output?
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Mitchell Hentges [:mhentges] 🦀 from comment #2)
Hey :cpeterson, we found out the core issue in that related bug:
TASKCLUSTER_ROOT_URL
was set to the old Taskcluster instance.
Is that what's causing your failure?If not, can you apply this patch (
hg import --no-commit debug-artifact.patch
) and paste your output?
mach bootstrap still fails with that patch attached. I'll attach my mach log. I haven't updated my hg clone in a couple days, if that matters.
Reporter | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
mach bootstrap still fails with that patch attached.
That's understandable, that patch just adds some helpful print()
s to debug the issue.
Hmm, in that most-recent log, it looks like you're running into a different issue.
Rather than seeing
Could not find artifacts for a toolchain build named ...
it looks like you're instead seeing
ModuleNotFoundError: No module named 'zstandard'
There's a simple workaround for that issue here.
Can you apply that workaround and try again? If you start running into "Could not find artifacts ..." again, then apply my "debug-artifact-with-urls" patch and submit the ol' logs again :)
Reporter | ||
Comment 6•5 years ago
|
||
(In reply to Mitchell Hentges [:mhentges] 🦀 from comment #5)
There's a simple workaround for that issue here.
Can you apply that workaround and try again? If you start running into "Could not find artifacts ..." again, then apply my "debug-artifact-with-urls" patch and submit the ol' logs again :)
After applying your patch from comment 2 above and deleting ~/.mozbuild/_virtualenvs
as suggested in bug 1660790 comment 3, I was able to successfully run mach bootstrap! 👍
Assignee | ||
Comment 7•4 years ago
|
||
That's good news! I doubt the patch had any effect, since it's a no-op other than adding print statements.
I'll close this for now, but please re-open if you run into the issue again :)
Description
•