-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 more begin_panic
normalizations to panic backtrace tests
#134781
Conversation
r? @SparrowLii rustbot has assigned @SparrowLii. Use |
cc @Mark-Simulacrum @jieyouxu since this related with #133997 |
It seems reasonable if only to suppress the local failures (but which are not super important for the tests themselves). I don't know the precise reason for the variations, but one possible cause is that the share generics could possibly induce platform-specific behavior in what gets shared and what doesn't (leading to backtrace differences). |
I was able to isolate the difference to I don't know precisely why that triggers it, or why it only appears to affect macOS, but backtraces are subject to so much platform-specific behaviour that I don't feel much need to dig further than that. |
Yeah, I think that's very reasonable. |
@bors r=SparrowLii,jieyouxu rollup |
…ieyouxu Add more `begin_panic` normalizations to panic backtrace tests Since rust-lang#123244, these tests have started failing locally on some systems (rust-lang#133997) due to minor variations in how `begin_panic` is printed in the backtrace. The variation appears to occur on macOS when `rust.debuginfo-level = "line-tables-only"` is set, which is the default in `config.compiler.toml`. It does not occur when the debuginfo level is set to 1. The variation doesn't seem relevant to these tests, so this PR simply adds another custom normalization rule to account for the variation. --- Will conflict with rust-lang#134759.
Rollup of 4 pull requests Successful merges: - rust-lang#134664 (Account for removal of multiline span in suggestion) - rust-lang#134774 (fix default-backtrace-ice test) - rust-lang#134781 (Add more `begin_panic` normalizations to panic backtrace tests) - rust-lang#134784 (Miri subtree update) r? `@ghost` `@rustbot` modify labels: rollup
…llaumeGomez Rollup of 4 pull requests Successful merges: - rust-lang#134656 (Migrate `incr-add-rust-src-component` to rmake) - rust-lang#134664 (Account for removal of multiline span in suggestion) - rust-lang#134772 (Improve/cleanup rustdoc code) - rust-lang#134781 (Add more `begin_panic` normalizations to panic backtrace tests) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#134781 - Zalathar:backtrace, r=SparrowLii,jieyouxu Add more `begin_panic` normalizations to panic backtrace tests Since rust-lang#123244, these tests have started failing locally on some systems (rust-lang#133997) due to minor variations in how `begin_panic` is printed in the backtrace. The variation appears to occur on macOS when `rust.debuginfo-level = "line-tables-only"` is set, which is the default in `config.compiler.toml`. It does not occur when the debuginfo level is set to 1. The variation doesn't seem relevant to these tests, so this PR simply adds another custom normalization rule to account for the variation. --- Will conflict with rust-lang#134759.
Since #123244, these tests have started failing locally on some systems (#133997) due to minor variations in how
begin_panic
is printed in the backtrace.The variation appears to occur on macOS when
rust.debuginfo-level = "line-tables-only"
is set, which is the default inconfig.compiler.toml
. It does not occur when the debuginfo level is set to 1.The variation doesn't seem relevant to these tests, so this PR simply adds another custom normalization rule to account for the variation.
Will conflict with #134759.