-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split the test suite into multiple binaries #2743
Conversation
This isn't really necessary and we can do setup manually in a few cases and lazily do it in all the others.
r? @wycats (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ |
📌 Commit aa70276 has been approved by |
⌛ Testing commit aa70276 with merge 459399d... |
💔 Test failed - cargo-win-msvc-64 |
aa70276
to
0151deb
Compare
@bors: r+ |
📌 Commit 0151deb has been approved by |
⌛ Testing commit 0151deb with merge ebb006a... |
@bors: r+ |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 0151deb has been approved by |
💔 Test failed - cargo-win-msvc-64 |
@bors: retry On Wed, May 25, 2016 at 5:33 PM, bors notifications@github.com wrote:
|
Split the test suite into multiple binaries Helps reduce compile time of tests, more ergonomic names to type, more conventional configuration, and makes it basically easier to work with. The previous `support` module is now a separate `cargotest` crate.
💔 Test failed - cargo-win-msvc-64 |
@bors: retry On Wed, May 25, 2016 at 5:51 PM, bors notifications@github.com wrote:
|
⚡ Previous build results for cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64 are reusable. Rebuilding only cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64... |
💔 Test failed - cargo-win-gnu-32 |
0151deb
to
237b17d
Compare
@bors: r+ |
📌 Commit 237b17d has been approved by |
⌛ Testing commit 237b17d with merge 52ad04c... |
💔 Test failed - cargo-win-msvc-64 |
237b17d
to
f4b7134
Compare
@bors: r+ |
📌 Commit f4b7134 has been approved by |
⌛ Testing commit f4b7134 with merge ded5328... |
💔 Test failed - cargo-win-msvc-64 |
Compiling everything in one binary was getting annoying as it just took forever to build, instead shard it all up so we can build just particular test suites at a time.
f4b7134
to
763ba53
Compare
@bors: r+ |
📌 Commit 763ba53 has been approved by |
⌛ Testing commit 763ba53 with merge 5b22575... |
💔 Test failed - cargo-win-gnu-32 |
@bors: retry On Wed, May 25, 2016 at 9:40 PM, bors notifications@github.com wrote:
|
Split the test suite into multiple binaries Helps reduce compile time of tests, more ergonomic names to type, more conventional configuration, and makes it basically easier to work with. The previous `support` module is now a separate `cargotest` crate.
☀️ 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 |
Helps reduce compile time of tests, more ergonomic names to type, more conventional configuration, and makes it basically easier to work with.
The previous
support
module is now a separatecargotest
crate.