-
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
ci: temporarily disable overflow checks again. #90228
ci: temporarily disable overflow checks again. #90228
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
cc @hkratz |
482458b
to
700c61c
Compare
. rust-lang#89776 enabled overflow checks in CI but these lead to two failures already: rust-lang#90042 (comment) rust-lang#90222 (comment) The (first?) problem has been identified: rust-lang#90227 This PR temporarily disables the overflow checks again so we don't have to deal with the "spurious" CI failures until rustc-rayon is fixed. Zulip discussion: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/ci.20failed.20with.20.20.22attempt.20to.20subtract.20with.20overflow.22
700c61c
to
edae201
Compare
Can we limit this just to rustc-rayon (via an override in Cargo.toml) or builders enabling the parallel compiler, without which rustc-rayon shouldn't be used iirc? |
I tried to somehow modify cargo flags of the rustc-rayon dependency via rustcs Cargo.toml but without success. :/ |
Putting this in the top-level Cargo.toml should work: [profile.release.package.rustc-rayon-core]
overflow-checks = false We already do this for compiler-builtins. Edited: Overflow is indeed in rustc-rayon-core. |
Don't we need it in rustc-rayon-core? Maybe I'm misremembering but I saw it mentioned somewhere |
@hkratz can you open a pr? I'd close this in favor of a cargo.toml fix then :) |
Great, thank you! :) |
#89776 enabled overflow checks in CI but these lead to two failures already:
#90042 (comment)
#90222 (comment)
The (first?) problem has been identified: #90227
This PR temporarily disables the overflow checks again so we don't have to deal with the "spurious" CI failures until rustc-rayon is fixed.
Zulip discussion: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/ci.20failed.20with.20.20.22attempt.20to.20subtract.20with.20overflow.22