Conversation
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
|
@bors: r+ |
|
📌 Commit 25223cf8893fade36ade61e0c216532bc9aa6ac4 has been approved by |
|
⌛ Testing commit 25223cf8893fade36ade61e0c216532bc9aa6ac4 with merge 29e3e9b9f31112360e7db4a0d91ab7706142f1af... |
|
💔 Test failed - status-appveyor |
|
🤔 It passes locally for me, and I'm stumped as to how it could fail. @alexcrichton let me know if you have any ideas why it would fail, otherwise I can try investigating more. |
|
@ehuss Are you testing on Windows? |
|
@kennytm yea, tested on windows and mac within the rust tree. The test has also been passing on Cargo's appveyor. |
|
git's error message is quite funny: That I think it'd be fine to force Cargo to either whitelist this test to not run (like we do for cross-compilation tests) and then only run it on Cargo's CI. |
|
Ah, I can confirm the mingw /usr/bin/git does not like windows-style file urls. Do you have a preferred way to detect this scenario? A new env var? Check for "windows" in |
|
It's probably easiest to do what the cross-compilation tests do which is to execute the test unless a "weird env var" is set. The tests here in this repository would set such an environment variable, but in Cargo we'd continue to run the test by default. I suppose a real fix is to add this to Cargo itself and figure out the best |
|
Updated to skip the test (I think this one place should be sufficient, though I'm not certain). I could add an |
|
@bors: r+ |
|
📌 Commit f9f06c34a520e67aa1bcb28520f55859f5b37812 has been approved by |
|
@alexcrichton updated |
|
@bors: r+ p=1 |
|
📌 Commit 0120e17 has been approved by |
|
⌛ Testing commit 0120e17 with merge da8b207de49fec3567ad7dce84c572c95646af04... |
|
💔 Test failed - status-travis |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
Looks like an unrelated error. |
(done by matthiaskrgr, but I authored ehuss)
…Mark-Simulacrum Stabilize edition 2018; also updates Clippy, RLS and Cargo Supersedes #53999 , #53935 Clippy build was failing there because crate_visibility_modifier feature was taken out of edition 2018 and clippy used it. The clippy update enables the corresponding feature explicitly. r? @Mark-Simulacrum
|
@bors: retry delegate+ |
|
✌️ @ehuss can now approve this pull request |
|
☔ The latest upstream changes (presumably #54057) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Merged in #54057. |
cargo
32 commits in 0ec7281b9c36ca7f724bfac8b029633910270a48..2fb77a49b43bf7266793c07a19a06749e6a8ad5a
2018-08-20 21:18:45 +0000 to 2018-09-07 17:00:19 +0000
cargo installignore .cargo/config (makecargo installignore .cargo/config cargo#5874)cargo fixto rebuild (Forcecargo fixto rebuild cargo#5944)--allow-stagedtocargo fix(Add--allow-stagedtocargo fixcargo#5943)hamcrestmodule (Remove Cargo's internalhamcrestmodule cargo#5945)pathdependencies (Only use non-absolute paths forpathdependencies cargo#5935)codemap::Spanchange. (Fix test failure on nightly due tocodemap::Spanchange. cargo#5937)cargo installdeprecation messaging (Improve thecargo installdeprecation messaging cargo#5925)required-featurestoSerializedTarget(Addrequired-featurestoSerializedTargetcargo#5902)Added:
use_the_clitest for rust repo. (Add a way to skip theuse_the_clitest for rust repo. cargo#5976)Added:
cargo newto 2018 (Change the default edition forcargo newto 2018 cargo#5989)editionkey and addcargo new --edition(Stabilizeeditionkey and addcargo new --editioncargo#5984)RUSTC_WRAPPER(fix: Fix unusual errors withRUSTC_WRAPPERcargo#5983)rls
6 commits in cf6358a00540a83dcc6e8c243f3306ccdbb9c354..ac2e802ae9115786196a498e22086d403efd95a4
2018-09-04 14:46:47 +0200 to 2018-09-08 00:17:42 +0200