-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Re-enable rustc_codegen_gcc
tests in CI
#118463
Conversation
This comment has been minimized.
This comment has been minimized.
... at least we know the tests really did run this time! 😅 |
Ah. Well, I'll try to fix it tomorrow. 😅 |
This comment has been minimized.
This comment has been minimized.
8d9f0c1
to
1c021ff
Compare
1c021ff
to
dc20566
Compare
CI passed so since we know it works, we can now check if the |
It was unneeded, great! |
Thanks for the collaboration! Let's roll for a neutral reviewer... r? infra-ci |
Seems like they're a bit underwater. Well in this case I think it's fine since we reviewed each other's code already. @bors r=cuviper,GuillaumeGomez |
☀️ Test successful - checks-actions |
…umeGomez Fix `rustc_codegen_gcc` build and tests failure in CI rust-lang#118463 seems to have broke the PR CI, more specificaly the `x86_64-gnu-llvm-16` builder which [fail with](https://github.com/rust-lang/rust/actions/runs/7128709674/job/19411205695?pr=118705#step:26:1668): ``` Building stage1 codegen backend gcc (x86_64-unknown-linux-gnu) Compiling libc v0.2.147 Compiling rustix v0.38.8 Compiling memchr v2.5.0 Compiling bitflags v2.4.0 Compiling linux-raw-sys v0.4.5 Compiling fastrand v2.0.0 Compiling smallvec v1.10.0 error: invalid `--check-cfg` argument: `values(freebsd10)` (expected `cfg(name, values("value1", "value2", ... "valueN"))`) error: could not compile `libc` (lib) due to previous error ``` Updating to `libc` version 0.2.150 fixes the build issue since it includes the support for the new check-cfg syntax. Then it [failed](https://github.com/rust-lang/rust/actions/runs/7129280743/job/19413025132?pr=118706#step:26:2218) with a missing `#![allow(internal_features)]` in one of the example. r? `@GuillaumeGomez`
Finished benchmarking commit (b9540b7): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 675.32s -> 674.699s (-0.09%) |
When #117947 dropped llvm-15 from CI, we neglected to copy #117313's changes to enable
rustc_codegen_gcc
testing to the new base llvm-16. This is now restored, as well as copying the setup to llvm-17 as well so we hopefully won't miss it next time.In addition, due to case mismatch in
$extra_env
updates indocker/run.sh
, I think it wasn't actually getting enabled before, but this should now be fixed. I also avoided the linker hack forlibgccjit.so
that was present before, because that's not needed if the version matches the basegcc
used for linking.r? GuillaumeGomez