Summary
On hosts (e.g. aarch64-apple-darwin) where we don't built "alt CI LLVM" (CI LLVM with assertions enabled), a configuration like
[llvm]
download-ci-llvm = true
assertions = true
will fail to find a CI LLVM from the alternative channel that has "compatible LLVM config" (namely with assertions enabled), yet prints zero warnings/errors, and then tries to checkout llvm submodule and build it locally.
When download-ci-llvm = true, the user intention is to force usage of CI LLVM. We should at least show a warning here, or error, and not silently try to build LLVM.
Command used
Expected behaviour
Warning or error for incompatible LLVM config versus available CI LLVM artifacts
Actual behaviour
0 errors 0 warnings
Bootstrap configuration (bootstrap.toml)
[llvm]
download-ci-llvm = true
assertions = true
Operating system
aarch64-apple-darwin host
HEAD
a04c7a0
Additional context
N/A
Summary
On hosts (e.g.
aarch64-apple-darwin) where we don't built "alt CI LLVM" (CI LLVM with assertions enabled), a configuration likewill fail to find a CI LLVM from the alternative channel that has "compatible LLVM config" (namely with assertions enabled), yet prints zero warnings/errors, and then tries to checkout llvm submodule and build it locally.
When
download-ci-llvm = true, the user intention is to force usage of CI LLVM. We should at least show a warning here, or error, and not silently try to build LLVM.Command used
Expected behaviour
Warning or error for incompatible LLVM config versus available CI LLVM artifacts
Actual behaviour
0 errors 0 warnings
Bootstrap configuration (bootstrap.toml)
Operating system
aarch64-apple-darwinhostHEAD
a04c7a0
Additional context
N/A