Uh oh!
There was an error while loading. Please reload this page.
don't leak environment variables into test process - #31256
Conversation
rust-highfive
commented
Jan 28, 2016
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
nagisa
commented
Jan 28, 2016
@bors r+ rollup 97be317 |
bors
commented
Jan 28, 2016
📌 Commit 97be317 has been approved by |
bors
commented
Jan 28, 2016
⌛ Testing commit 97be317 with merge 1d4887e... |
bors
commented
Jan 28, 2016
💔 Test failed - auto-win-gnu-64-opt |
nagisa
commented
Jan 28, 2016
The failure filled as #31259 |
alexcrichton
commented
Jan 28, 2016
I'd recommend an explicit |
If the tests were run with `RUST_BACKTRACE=1 make check` this test failed. If they were run without it it succeeded. We need to use `env_remove` instead of `env_clear` because the latter will never work on windows
oli-obk
commented
Jan 29, 2016
fixed |
nagisa
commented
Jan 29, 2016
if the tests were run with `RUST_BACKTRACE=1 make check` this test failed. If they were run without `RUST_BACKTRACE=1` it succeeded.
if the tests were run with
RUST_BACKTRACE=1 make checkthis test failed. If they were run withoutRUST_BACKTRACE=1it succeeded.