Uh oh!
There was an error while loading. Please reload this page.
Add some more repos to cargotest - #37149
Conversation
rust-highfive
commented
Oct 13, 2016
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (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. |
alexcrichton
commented
Oct 13, 2016
@bors: r+ |
bors
commented
Oct 13, 2016
📌 Commit 4f71566 has been approved by |
There was a problem hiding this comment.
Ugh, how embarrassing... Looks like circumventing my editor's insistence on 80-char lines also impeded its automatically fixing those. My apologies.
alexcrichton
commented
Oct 31, 2016
@bors: r+ |
bors
commented
Oct 31, 2016
📌 Commit 7d775e1 has been approved by |
bors
commented
Oct 31, 2016
⌛ Testing commit 7d775e1 with merge 5a54b72... |
bors
commented
Oct 31, 2016
💔 Test failed - auto-linux-64-cargotest |
edunham
commented
Nov 7, 2016
Sorry, I ought to have linted locally. Fixed missing comma and rebased onto current master branch. |
sanxiyn
commented
Nov 7, 2016
@bors r+ |
bors
commented
Nov 7, 2016
📌 Commit 1e951ec has been approved by |
bors
commented
Nov 7, 2016
⌛ Testing commit 1e951ec with merge d70463d... |
bors
commented
Nov 7, 2016
💔 Test failed - auto-linux-cross-opt |
sanxiyn
commented
Nov 8, 2016
@bors retry crates.io outage. |
bors
commented
Nov 8, 2016
⌛ Testing commit 1e951ec with merge fb54b2f... |
bors
commented
Nov 8, 2016
💔 Test failed - auto-win-msvc-64-cargotest |
sanxiyn
commented
Nov 9, 2016
ripgrep failed two tests (symlink_follow, symlink_nofollow) on Windows. |
alexcrichton
commented
Nov 10, 2016
cc @BurntSushi do you know of any tricks needed to get the ripgrep test suite passing on Windows? If it's too hard for the bots then we can perhaps just exclude the suite for now and add the other repos. |
@alexcrichton Oh interesting! Those tests pass on AppVeyor. However, there is at least one other test on Windows dealing with symlinks that I explicitly skip on Windows because it fails on AppVeyor for the same reason (permission error) I don't think I did any tricks though. I'd be OK skipping them in ripgrep proper, because symlinks on Windows are pretty janky anyway. Other ideas? |
alexcrichton
commented
Nov 10, 2016
I do recall there's some Windows permission to allow users to create symlinks, so maybe appveyor has that enabled by default? (our buildbots don't). But yeah if you want to skip these in the ripgrep test suite we could update to include that! |
For some reason, these work on AppVeyor but not in other build systems. Let's just disable them. See: rust-lang/rust#37149
BurntSushi
commented
Nov 11, 2016
OK, I disabled the tests, which should take effect in the next release. |
alexcrichton
commented
Nov 11, 2016
Awesome, thanks @BurntSushi! @edunham want to update git git repo for ripgrep and we can retry? |
bors
commented
Dec 29, 2016
💔 Test failed - status-travis |
alexcrichton
commented
Dec 29, 2016
via email
| … On Thu, Dec 29, 2016 at 11:34 AM, bors ***@***.***> wrote:
💔 Test failed - status-travis
<https://travis-ci.org/rust-lang/rust/builds/187525618>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95GU4AWrg12V6lT6bJI8WZkh0ypgeks5rNAswgaJpZM4KWMBB>
.
|
bors
commented
Dec 29, 2016
⌛ Testing commit a0f3c93 with merge 9c145c2... |
bors
commented
Dec 29, 2016
💔 Test failed - status-appveyor |
alexcrichton
commented
Dec 29, 2016
via email
@bors: retry
* network error …On Thu, Dec 29, 2016 at 2:19 PM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.1313>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95JfHa1bygutKgHWw3lQjQiWiIh3Xks5rNDH_gaJpZM4KWMBB>
.
|
Add some more repos to cargotest From suggestions at https://users.rust-lang.org/t/what-stable-rust-applications-do-you-use-frequently/7618 This adds some applications which use stable Rust and come with their own lockfiles in their respective trees. ripgrep, xsv, and bins have 33 unique dependencies between them. I alphabetized the list by project name because that seems tidier. r? @brson
bors
commented
Dec 30, 2016
⌛ Testing commit a0f3c93 with merge 1ac816c... |
alexcrichton
commented
Dec 30, 2016
@bors: retry |
bors
commented
Dec 30, 2016
⌛ Testing commit a0f3c93 with merge 738e016... |
alexcrichton
commented
Dec 30, 2016
@bors: retry |
bors
commented
Dec 30, 2016
⌛ Testing commit a0f3c93 with merge b8af359... |
alexcrichton
commented
Dec 30, 2016
@bors: retry |
bors
commented
Dec 30, 2016
⌛ Testing commit a0f3c93 with merge 42d4de0... |
bors
commented
Dec 30, 2016
💔 Test failed - status-travis |
This was intended to land in rust-lang#37149 but I ended up backing it out to land the rollup (rust-lang#38697) last night as I was itching to do so. This morning though xsv has been fixed now (BurntSushi/xsv#53) so we should be able to add it!
cargotest: Add xsv to tested crates This was intended to land in #37149 but I ended up backing it out to land the rollup (#38697) last night as I was itching to do so. This morning though xsv has been fixed now (BurntSushi/xsv#53) so we should be able to add it!
From suggestions at https://users.rust-lang.org/t/what-stable-rust-applications-do-you-use-frequently/7618
This adds some applications which use stable Rust and come with their own lockfiles in their respective trees.
ripgrep, xsv, and bins have 33 unique dependencies between them.
I alphabetized the list by project name because that seems tidier.
r? @brson