Fix tests for RUST_NEW_ERROR_FORMAT #2742
Conversation
|
r? @wycats (rust_highfive has picked a reviewer for you, use r? to override) |
|
☔ The latest upstream changes (presumably #2743) made this pull request unmergeable. Please resolve the merge conflicts. |
A few tests were a bit too strict in the output they were looking for, this instead relaxes some assertions to just what we're interested in.
alexcrichton
force-pushed
the
new-error-format
branch
from
1c44978
to
d38bb34
Compare
|
@bors r+ |
|
📌 Commit d38bb34 has been approved by |
|
⌛ Testing commit d38bb34 with merge 357d462... |
|
💔 Test failed - cargo-win-msvc-32 |
|
@bors: retry On Thu, May 26, 2016 at 4:46 PM, bors notifications@github.com wrote:
|
Fix tests for RUST_NEW_ERROR_FORMAT A few tests were a bit too strict in the output they were looking for, this instead relaxes some assertions to just what we're interested in.
|
☀️ Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
A few tests were a bit too strict in the output they were looking for, this
instead relaxes some assertions to just what we're interested in.