Closed
Description
We promise that our GNU rustc toolchains won't need a glibc newer than a certain version (https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kernel-requirements.html), but we don't currently have a test that would actually test this. It can be quite easy to inadvertedly bump the glibc, for example when updating base images of the OS in a container that builds the dist
toolchain on CI.
It would be nice of we had some kind of (run-make?) test that checks the exact version of glibc used by a toolchain compiled on CI. It should be executed explicitly in specific CI runners, so that we can vary the required glibc version per CI job (and thus per tier/platform).
Metadata
Metadata
Assignees
Labels
Area: The testsuite used to check the correctness of rustcCategory: An issue proposing an enhancement or a PR with one.Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the compiler team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.