-
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
spurious test failure: ui\panics\panic-short-backtrace-windows-x86_64.rs on x86_64-msvc-2 #92000
Comments
@rustbot label +O-windows |
This is causing a lot of spurious failures, as evidenced by the numerous "mentioned this issue" items in this issue. Should this test be ignored temporarily until the underlying problem is identified and fixed? cc @rust-lang/infra |
@rustbot modify labels: +O-windows-msvc |
I'm on PTO but I'll put this on my list of things to look into when I get back next week. In the mean time, disabling the test seems reasonable to me. |
…imulacrum Ignore flaky `panic-short-backtrace-windows-x86_64.rs` test for now Mitigates (but does not fix) rust-lang#92000. It has been causing a lot of spurious test failures recently that slow down the bors queue.
…ulacrum Ignore flaky `panic-short-backtrace-windows-x86_64.rs` test for now Mitigates (but does not fix) rust-lang#92000. It has been causing a lot of spurious test failures recently that slow down the bors queue.
The test is now ignored, so there shouldn't be any more spurious failures. However, the underlying issue isn't fixed yet. |
The comment in the test seems potentially relevant: rust/src/test/ui/panics/panic-short-backtrace-windows-x86_64.rs Lines 17 to 20 in f1ce0e6
If |
We could modify the |
The
ui\panics\panic-short-backtrace-windows-x86_64.rs
test seems to randomly fail onx86_64-msvc-2
sometimes.https://pipelines.actions.githubusercontent.com/DhU3eyB11Ei4viT99vzh0CpKzg7REqx1Nup2tB9LzmxBcoHdbh/_apis/pipelines/1/runs/14339/signedlogcontent/31?urlExpires=2021-12-16T12%3A15%3A54.9212371Z&urlSigningMethod=HMACV1&urlSignature=%2FsTx%2F9cdlfikD4rjevyZM9XXK2s%2BqXIVMXzWYgCm%2BpI%3D
The text was updated successfully, but these errors were encountered: