Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should RUST_BACKTRACE be set? #117

Open
nbigaouette opened this issue Jan 3, 2019 · 0 comments
Open

Should RUST_BACKTRACE be set? #117

nbigaouette opened this issue Jan 3, 2019 · 0 comments

Comments

@nbigaouette
Copy link

A unit test failure in my Travis CI failed to show a proper backtrace. Looking at the .travis.yml file it does not seems that RUST_BACKTRACE=1 is set.

Would:

env:
  global:
    - RUST_BACKTRACE=1

be sufficient? (with the same for appveyor?)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nbigaouette