-
Notifications
You must be signed in to change notification settings - Fork 13.3k
backtrace tidy #25741
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
backtrace tidy #25741
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
@@ -19,4 +19,6 @@ endif | |||
print-%: | |||
@echo $*=$($*) | |||
|
|||
export RUST_BACKTRACE=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we may want to omit this for now, this causes all tests to emit backtraces which may not always be desirable (especially the test harness itself). The change below looks good to me though!
Oh! I hadn't considered that. Removed the second commit. |
The second commit seems reasonable to me but I can remove if it's contentious. The first is purely cosmetic but has been irking me for ages.
The second commit seems reasonable to me but I can remove if it's contentious. The first is purely cosmetic but has been irking me for ages.