-
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
Add a hack to workaround MSVC CI issues #129509
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
Hm, I seem to recall us having every-30-second printing that was needed for avoidance of some kind of cancellation mechanism. But maybe not actually needed anymore. r=me |
@bors r=Mark-Simulacrum rollup |
@bors p=1 so this will be picked up if the CI keeps failing |
…-Simulacrum Add a hack to workaround MSVC CI issues I'm still attempting to figure out the issue but the failure rate atm seems really high so I'd like to propose an interim hack. This adds a single delay of 5 minutes, which is absurdly long in CPU time but practically nothing compared to overall CI time.
…iaskrgr Rollup of 10 pull requests Successful merges: - rust-lang#128596 (stabilize const_fn_floating_point_arithmetic) - rust-lang#129199 (make writes_through_immutable_pointer a hard error) - rust-lang#129246 (Retroactively feature gate `ConstArgKind::Path`) - rust-lang#129290 (Pin `cc` to 1.0.105) - rust-lang#129323 (Implement `ptr::fn_addr_eq`) - rust-lang#129500 (remove invalid `TyCompat` relation for effects) - rust-lang#129501 (panicking: improve hint for Miri's RUST_BACKTRACE behavior) - rust-lang#129505 (interpret: ImmTy: tighten sanity checks in offset logic) - rust-lang#129509 (Add a hack to workaround MSVC CI issues) - rust-lang#129510 (Fix `elided_named_lifetimes` in code) r? `@ghost` `@rustbot` modify labels: rollup
…imulacrum Add a hack to workaround MSVC CI issues I'm still attempting to figure out the issue but the failure rate atm seems really high so I'd like to propose an interim hack. This adds a single delay of 5 minutes, which is absurdly long in CPU time but practically nothing compared to overall CI time.
@bors r- That it passed in my tests seems to just have been by chance unfortunately. I'll need to find another approach, |
I'm still attempting to figure out the issue but the failure rate atm seems really high so I'd like to propose an interim hack.
This adds a single delay of 5 minutes, which is absurdly long in CPU time but practically nothing compared to overall CI time.