In order that we might succeed in getting through our tests,
until we can properly diagnose and correct for whatever causes the
dist tests alone to fail in such spectacular ways, limit the dist
tests to a single thread to reduce the chance that they fail on
Windows CI.
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
We need EXE extension support in the deployment script so that
Windows can deploy rustup-init.exe and friends
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
To allow us to ensure that we do not have unexpected version strings
due to dirty builds etc, dump the testament after the build but before
running the tests. We can't do this for unusual cross-builds but
for the most part we can do it on at least one of each of our major
platforms.
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
When building for `linux-gnu` targets, we need to be careful about which
versioned GLIBC symbols we'll link, as this sets the minimum supportable
system version in ABI. The images in rust-lang/rust/src/ci/docker/ have
already taken this into account, and since they're uploaded to S3, we
can just use those exact images to get the same ABI compatibility.
The builds for mips*, powerpc*, and s390x were identified in #1681 as
having newer glibc symbols than rustc, so those are now changed to use
rust's docker images. In the future, we might want to do this for other
architectures too, so all toolchains are in sync.
In order to ensure that we don't get odd formatting changes
mixed in with future PRs, verify the formatting during the CI
run if all tests pass.
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
This commit updates the CI builds for rustup to always build
`openssl-src` from crates.io instead of having a baked-in build of
OpenSSL. This matches what Cargo has switched to as well, and is
intended to centralize OpenSSL updates to one crates.io crate.
This also modernizes the docker containers and builds a bit to remove
the need for some scripts here and there.
