user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

bootstrap: skip r-a main tests against 32-bit targets

Browse source 
We don't really have a good way to get the target pointer width in
bootstrap (yet), so I had to resort to hacky target tuple substring
matches.

This commit currently only gates on `i686-*` targets, which are 32-bits,
and does not try to gate on `i586-*` targets (I need to run try jobs to
check if r-a tests actually get run.)
This commit is contained in:
Jieyou Xu 2025-12-11 20:57:34 +08:00
parent 24f00b63ef
commit 15e49699ca
No known key found for this signature in database
GPG key ID: 045B995028EA6AFC
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
src/bootstrap/src/core/build_steps/test.rs
View file

@ -468,6 +468,19 @@ impl Step for RustAnalyzer {
let build_compiler = self.compilers.build_compiler();
let target = self.compilers.target();
// NOTE: rust-analyzer repo currently (as of 2025-12-11) does not run tests against 32-bit
// targets, so we also don't run them in rust-lang/rust CI (because that will just mean that
// subtree syncs will keep getting 32-bit-specific failures that are not observed in
// rust-analyzer repo CI).
//
// Some 32-bit specific failures include e.g. target pointer width specific hashes.
// FIXME: eventually, we should probably reduce the amount of target tuple substring
// matching in bootstrap.
if target.starts_with("i686") {
return;
}
let mut cargo = tool::prepare_tool_cargo(
builder,
build_compiler,