-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Fix rustc_codegen_gcc
build and tests failure in CI
#118706
Conversation
Some changes occurred in compiler/rustc_codegen_gcc cc @antoyo |
This comment has been minimized.
This comment has been minimized.
Seems like we would now need to specify If it is needed for many tests, it might be simpler to just set |
✌️ @Urgau, you can now approve this pull request! If @GuillaumeGomez told you to " |
rustc_codegen_gcc
build and tests failure in CI
Failed to set assignee to
|
@bors r=@GuillaumeGomez p=1 |
☀️ Test successful - checks-actions |
Finished benchmarking commit (f16c81f): 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 673.714s -> 674.821s (0.16%) |
…askrgr Fix again `rustc_codegen_gcc` tests Similar to rust-lang#118706 r? `@GuillaumeGomez`
…askrgr Fix again `rustc_codegen_gcc` tests Similar to rust-lang#118706 r? `@GuillaumeGomez`
Rollup merge of rust-lang#118835 - Urgau:fix-rccg-gcc-tests, r=matthiaskrgr Fix again `rustc_codegen_gcc` tests Similar to rust-lang#118706 r? `@GuillaumeGomez`
#118463 seems to have broke the PR CI, more specificaly the
x86_64-gnu-llvm-16
builder which fail with: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 with a missing
#![allow(internal_features)]
in one of the example.r? @GuillaumeGomez