Closed
Bug 1836957
Opened 2 years ago
Closed 2 years ago
Could not find artifacts for a toolchain build named `toolchain-macosx64-aarch64-clang`.
Categories
(Firefox Build System :: Toolchains, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: alexboy94, Unassigned)
References
Details
Steps to reproduce:
On esr115, commit 77f9866031c0c2a29783aa5c394e8a2fb4e87fb7, attempting to ./mach build
fails to bootstrap the clang toolchain.
Actual results:
0:00.74 checking for vcs source checkout... git
0:00.77 checking for a shell... /bin/sh
0:00.79 checking for host system type... aarch64-apple-darwin22.5.0
0:00.79 checking for target system type... aarch64-apple-darwin22.5.0
0:01.00 checking whether cross compiling... no
0:01.08 checking for Python 3... /Users/akontos/Work/unified/obj-Darwin-arm64/_virtualenvs/build/bin/python (3.9.6)
0:01.08 checking for git... /opt/homebrew/bin/git
0:01.12 checking for Git version... 2.41.0
0:01.13 checking for sparse checkout... no
0:02.51 checking for wget... /opt/homebrew/bin/wget
0:02.51 Installing bootstrapped toolchain in /Users/akontos/.mozbuild/MacOSX13.3.sdk
0:09.47 Installing bootstrapped toolchain in /Users/akontos/.mozbuild/clang
0:11.10 ERROR!!!!!! Could not find artifacts for a toolchain build named `toolchain-macosx64-aarch64-clang`. 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. 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.
Expected results:
Boostrap should have completed.
Reporter | ||
Comment 1•2 years ago
|
||
This error also occurs with sccache, cbindgen etc.
Comment 2•2 years ago
|
||
Works for me. Did you run ./mach bootstrap
after switching to esr115
?
Flags: needinfo?(alexboy94)
Reporter | ||
Comment 3•2 years ago
|
||
So bizarre, I have just tried again (bootstrap fails due to issues downloading the macOS SDK as in bug 1831491) with --enable-bootstrap
and it works! If this were to happen again, are there any more useful debugging steps I can take?
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(alexboy94)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•