Rollup merge of #101952 - Mark-Simulacrum:missing-fallback, r=ehuss

Avoid panicking on missing fallback

This just prints a message but continues on if a fallback is missing, which can happen when we're building a partial set of builders and producing a dev-static build from it (e.g., when no Apple builder runs at all).

Probably the more extensive fix is to allow the build-manifest invoker to specify the expected set of targets & hosts, but that's a far more extensive change. The main risk from this is that we accidentally start falling back to linux docs across all platforms without noticing. I'm not sure that we can do much about that though at this time.

cc `@ehuss` since IIRC you participated in adding this system

This comes up when building a test nightly from a try build, e.g., https://github.com/rust-lang/rust/pull/101855#issuecomment-1250123298. For now I'm going to manually cherry pick this onto that PR for testing purposes.
This commit is contained in:
Yuki Okushi 2022-09-22 09:03:52 +09:00 committed by GitHub
commit b08c8cb7e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -543,8 +543,18 @@ macro_rules! tarball_name {
for (substr, fallback_target) in fallback {
if target_name.contains(substr) {
let t = Target::from_compressed_tar(self, &tarball_name!(fallback_target));
// Fallbacks must always be available.
assert!(t.available);
// Fallbacks should typically be available on 'production' builds
// but may not be available for try builds, which only build one target by
// default. Ideally we'd gate this being a hard error on whether we're in a
// production build or not, but it's not information that's readily available
// here.
if !t.available {
eprintln!(
"{:?} not available for fallback",
tarball_name!(fallback_target)
);
continue;
}
return t;
}
}