-
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
Miri: port error backtraces to std::backtrace #71712
Conversation
I checked in the code that @bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit 30b32c6 with merge f1ecbbb3d28b7ebfb433e60f9a78a39ec8a6380a... |
☀️ Try build successful - checks-azure |
Queued f1ecbbb3d28b7ebfb433e60f9a78a39ec8a6380a with parent eece58a, future comparison URL. |
Finished benchmarking try commit f1ecbbb3d28b7ebfb433e60f9a78a39ec8a6380a, comparison URL. |
Well, I'd say there is no measurable difference. |
@bors r+ rollup |
📌 Commit 30b32c6 has been approved by |
Miri: port error backtraces to std::backtrace No need to pull in an external dependency if libstd already includes this feature (using the same dependency internally, but... still). r? @oli-obk
Miri: port error backtraces to std::backtrace No need to pull in an external dependency if libstd already includes this feature (using the same dependency internally, but... still). r? @oli-obk
Miri: port error backtraces to std::backtrace No need to pull in an external dependency if libstd already includes this feature (using the same dependency internally, but... still). r? @oli-obk
Rollup of 6 pull requests Successful merges: - rust-lang#71712 (Miri: port error backtraces to std::backtrace) - rust-lang#71736 (bootstrap: also apply unused-attributes hack without deny_warnings) - rust-lang#71738 (remove AllocId generalization of Pointer) - rust-lang#71739 (remove obsolete comment) - rust-lang#71781 (Uncomment test code for failure to use `Box::pin`) - rust-lang#71782 (Use a non-existent test path instead of clobbering /dev/null) Failed merges: r? @ghost
No need to pull in an external dependency if libstd already includes this feature (using the same dependency internally, but... still).
r? @oli-obk