Skip to content

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

Merged
merged 1 commit into from
May 27, 2015
Merged

backtrace tidy #25741

merged 1 commit into from
May 27, 2015

Conversation

richo
Copy link
Contributor

@richo richo commented May 24, 2015

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.

@rust-highfive
Copy link
Contributor

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@richo richo force-pushed the backtrace-message branch from 12aae76 to 648574d Compare May 24, 2015 02:52
@@ -19,4 +19,6 @@ endif
print-%:
@echo $*=$($*)

export RUST_BACKTRACE=1
Copy link
Member

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!

@richo richo force-pushed the backtrace-message branch from 648574d to 1b3465c Compare May 26, 2015 16:56
@richo
Copy link
Contributor Author

richo commented May 26, 2015

Oh! I hadn't considered that. Removed the second commit.

r? @alexcrichton

@alexcrichton
Copy link
Member

@bors: r+ 1b3465c

@bors
Copy link
Collaborator

bors commented May 27, 2015

⌛ Testing commit 1b3465c with merge a97b3ff...

bors added a commit that referenced this pull request May 27, 2015
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.
@bors bors merged commit 1b3465c into rust-lang:master May 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants