-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Update backtrace
in Cargo.lock
#140705
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
Update backtrace
in Cargo.lock
#140705
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
(I haven't fixed any test failures yet, want to see if they still exist) |
Could you update it again to 0.3.75? It was released 9 hours ago. |
Ran `cargo update -p backtrace`. This is needed to forward port the rust-gpu compiler backend. Subsumes rust-lang#140631. Was supposed to be fixed by rust-lang#140353, but there were test failures and the fix was backed out.
@Berrysoft done! Thanks for pointing that out. |
@bors r+ rollup=iffy |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing c6faa1b (parent) -> bfb44c8 (this PR) Test differencesShow 33146 test diffsStage 1
Stage 2
(and 16500 additional test diffs) Additionally, 16546 doctest diffs were found. These are ignored, as they are noisy. Job group index Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard bfb44c8155dc102358deeb27acef44abe030b30e --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (bfb44c8): comparison URL. Overall result: ❌ regressions - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -0.0%)This 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.
CyclesResults (primary -0.3%)This 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.
Binary sizeResults (secondary 0.0%)This 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.
Bootstrap: 773.028s -> 772.768s (-0.03%) |
…r=Zalathar Update miniz_oxide dependency of coverage_dump This was the final subproject that depended on ```miniz_oxide``` 0.7.x after the rest were when updating the ```backtrace-rs``` dependency in in rust-lang#140705. Older versions of ```miniz_oxide``` got hit by a [serious](rust-lang#132636) performance regression in rust 1.82 (which has been worked around in more recent versions of the library) so should really be avoided if possible (granted it only affects compression so not sure if it had much impact in practice here, though there have also been some other performance improvements since .) This also means no longer having to build two versions of miniz_oxide as everything can now use the same version, and no longer needing to build both ```adler``` and ```adler2```
Ran
cargo update -p backtrace
. This is needed to forward port the rust-gpu compiler backend.Subsumes #140631. Was supposed to be fixed by #140353, but there were test failures and the backtrace update was backed out.