-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check library crates for all tier 1 targets in PR CI #122401
Conversation
rustbot has assigned @Mark-Simulacrum. Use r? to explicitly pick a reviewer |
This comment has been minimized.
This comment has been minimized.
141281a
to
c196504
Compare
This comment has been minimized.
This comment has been minimized.
c196504
to
21ab400
Compare
This comment has been minimized.
This comment has been minimized.
21ab400
to
22cb6b5
Compare
This comment has been minimized.
This comment has been minimized.
dc6965d
to
ccca193
Compare
Ok, that's working now. And it only takes |
Cc #121519 |
ccca193
to
a52658d
Compare
Funnily enough I'd somehow completely forgotten about that issue when I first made this PR although it must have been in the back of my mind. |
a52658d
to
9d2641f
Compare
9d2641f
to
d5e5ef5
Compare
# Check library crates on all tier 1 targets. | ||
# We disable optimized compiler built-ins because that requires a C toolchain for the target. | ||
# We also skip the x86_64-unknown-linux-gnu target as it is well-tested by other jobs. | ||
python3 ../x.py check --stage 0 --set build.optimized-compiler-builtins=false core alloc std --target=aarch64-unknown-linux-gnu,i686-pc-windows-msvc,i686-unknown-linux-gnu,x86_64-apple-darwin,x86_64-pc-windows-gnu,x86_64-pc-windows-msvc && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this isn't including libtest and proc_macro, but those seem less likely to be target-dependent...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I was going by what tends to fail after an r+. Which is admittedly anecdotal and prone to biasing towards where code changes more frequently. But I figured that if it comes up then it's easy enough to add additional crates.
@bors r+ |
…enton Rollup of 7 pull requests Successful merges: - rust-lang#122323 (configure.py: add flag for loongarch64 musl-root) - rust-lang#122372 (prevent notifying the same changes more than once) - rust-lang#122390 (Bump windows-bindgen to 0.55.0) - rust-lang#122401 (Check library crates for all tier 1 targets in PR CI) - rust-lang#122489 (Bump `cargo update` PR more often) - rust-lang#122583 (Use `UnsafeCell` for fast constant thread locals) - rust-lang#122590 (bootstrap: Don't name things copy that are not copies) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#122401 - ChrisDenton:check-tier1, r=Mark-Simulacrum Check library crates for all tier 1 targets in PR CI Let's try checking all tier 1 targets. Shouldn't take much time. Not sure if this is the right place to put it or not but let's see if it works first.
Let's try checking all tier 1 targets. Shouldn't take much time.
Not sure if this is the right place to put it or not but let's see if it works first.