skip Codegen{GCC,Cranelift} when using CI rustc

[onur-ozkan]

CI rustc uses the default codegen backend, therefore we can't run CodegenGCC and CodegenCranelift tests when using it.

cc @bjorn3 (to make sure I am not doing anything wrong)

Fixes #123331

[rustbot]

r? @albertlarsan68

rustbot has assigned @albertlarsan68.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[bjorn3]

If you test stage2 rather than stage1, cg_clif and cg_gcc would be built, right?

[onur-ozkan]

If you test stage2 rather than stage1, cg_clif and cg_gcc would be built, right?

No, they will not. Here some more context:

rust/src/bootstrap/src/core/build_steps/compile.rs

Lines 1698 to 1709 in 36b6f9b

	// If we're downloading a compiler from CI, we can use the same compiler for all stages other than 0.
	if builder.download_rustc() {
	let sysroot =
	builder.ensure(Sysroot { compiler: target_compiler, force_recompile: false });
	// Ensure that `libLLVM.so` ends up in the newly created target directory,
	// so that tools using `rustc_private` can use it.
	dist::maybe_install_llvm_target(builder, target_compiler.host, &sysroot);
	// Lower stages use `ci-rustc-sysroot`, not stageN
	if target_compiler.stage == builder.top_stage {
	builder.info(&format!("Creating a sysroot for stage{stage} compiler (use `rustup toolchain link 'name' build/host/stage{stage}`)", stage=target_compiler.stage));
	}
	return target_compiler;

[onur-ozkan]

Do anyone have time to review this? @rust-lang/bootstrap

[Mark-Simulacrum]

@bors r+

This seems OK for now (given that it sounds like it doesn't work to not do this anyway), but I'd expect it to be possible for CI-downloaded rustc to link against a locally built cranelift/gcc codegen backend.

[bors]

📌 Commit 167e3ab has been approved by Mark-Simulacrum

It is now in the queue for this repository.