Skip to content

rustbuild: Touch up some test suites #33625

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

Merged
merged 3 commits into from
May 21, 2016

Conversation

alexcrichton
Copy link
Member

This adds in some missing test suites, primarily a few pretty suites. It also starts optimizing tests by default as the current test suite does, but also recognizes --disable-optimize-tests.

Currently the optimization of tests isn't recognized by crate tests because Cargo doesn't support the ability to compile an unoptimized test suite against an optimized library. Perhaps a feature to add, though!

@rust-highfive
Copy link
Contributor

r? @brson

(rust_highfive has picked a reviewer for you, use r? to override)

@aturon
Copy link
Member

aturon commented May 18, 2016

@bors: r+

@bors
Copy link
Collaborator

bors commented May 18, 2016

📌 Commit 0ccbc8b has been approved by aturon

@bors
Copy link
Collaborator

bors commented May 18, 2016

⌛ Testing commit 0ccbc8b with merge 8da02b3...

@bors
Copy link
Collaborator

bors commented May 18, 2016

💔 Test failed - auto-linux-64-opt-rustbuild

After a comparison with the current set of tests run it was discovered that
rustbuild accidentally wasn't running a few test suites. This commit adds back a
few more test suites:

* rfail-full
* pretty-rpass
* pretty-rpass-full
* pretty-rpass-valgrind
* pretty-rfail
* pretty-rfail-full
* librustc_bitflags unit tests
Currently rustbuild isn't detecting the `-O` flag for tests via the
`--disable-optimize-tests` or not command line flag to `./configure`, and this
commit patches up the support to pass `-O` by default.
Originally fixed in rust-lang#29961 the bug was unfortunately still present in the face
of crates using `#[macro_use]`. This commit refactors for the two code paths to
share common logic to ensure that they both pick up the same bug fix.

Closes rust-lang#33762
@alexcrichton
Copy link
Member Author

Blocked on #33762, I think I've fixed it, just confirming locally

@alexcrichton alexcrichton force-pushed the rustbuild-moar-tests branch from 0ccbc8b to 5f295f2 Compare May 20, 2016 21:41
@alexcrichton
Copy link
Member Author

@bors: r=aturon 5f295f2

@bors
Copy link
Collaborator

bors commented May 21, 2016

⌛ Testing commit 5f295f2 with merge 91e9073...

bors added a commit that referenced this pull request May 21, 2016
rustbuild: Touch up some test suites

This adds in some missing test suites, primarily a few pretty suites. It also starts optimizing tests by default as the current test suite does, but also recognizes `--disable-optimize-tests`.

Currently the optimization of tests isn't recognized by crate tests because Cargo doesn't support the ability to compile an unoptimized test suite against an optimized library. Perhaps a feature to add, though!
@bors bors merged commit 5f295f2 into rust-lang:master May 21, 2016
@alexcrichton alexcrichton deleted the rustbuild-moar-tests branch May 25, 2016 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants