Conversation
matklad
commented
May 8, 2016
- print "build failed" error to stderr (have not executed that line, but it should work :) )
- don't print "warning: warning:". Now the error looks like this:
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
Not sure why CI fails on Mac/beta. Looks like an unrelated race condition |
|
@bors: r+ 207d088e5b2a6ceb38d2237dc33b0a700be16f95 |
|
⌛ Testing commit 207d088 with merge 667a8ab... |
|
💔 Test failed - cargo-win-msvc-64 |
|
@bors: r+ |
|
📌 Commit 49b6d04 has been approved by |
|
⌛ Testing commit 49b6d04 with merge 52e9fbb... |
|
💔 Test failed - cargo-linux-64 |
|
@bors: retry On Mon, May 16, 2016 at 11:13 AM, bors [email protected] wrote:
|
|
⚡ Previous build results for cargo-cross-linux, cargo-win-gnu-32, cargo-win-gnu-64 are reusable. Rebuilding only cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-msvc-32, cargo-win-msvc-64... |
|
💔 Test failed - cargo-win-msvc-64 |
|
@bors: retry |
|
⌛ Testing commit 49b6d04 with merge ed20d7b... |
|
💔 Test failed - cargo-win-msvc-64 |
|
The other CI builds succeeded but this seems like a legitimate error happening 3 times in a row... |
|
It is indeed genuie: cross_compile tests always fail locally, so I don't run them. I've tried to fix the test in question. How should I run cross test locally? At the moment, I just |
|
You'll just need to install the cross-std, so if you're on rustup you can just do something like |
|
☔ The latest upstream changes (presumably #2722) made this pull request unmergeable. Please resolve the merge conflicts. |
* print "build failed" error to stderr * don't print "warning: warning:"