Skip to content
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

Add something like cargo test --no-fail-fast across all rustc tests #40219

Closed
cuviper opened this issue Mar 3, 2017 · 0 comments
Closed

Add something like cargo test --no-fail-fast across all rustc tests #40219

cuviper opened this issue Mar 3, 2017 · 0 comments
Labels
T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Comments

@cuviper
Copy link
Member

cuviper commented Mar 3, 2017

It would be nice to have a way in rustbuild to run ALL testsuites, even after a failure is encountered. For instance, on Fedora I know some of the alternate architectures aren't 100% passing, so I don't gate our builds on this, but I would still like to get a complete picture of the failures.

With the makefiles, I was using something like this to plow through and manually get a summary:

make check -k || python2 src/etc/check-summary tmp/*.log
@alexcrichton alexcrichton added the T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) label Mar 3, 2017
cuviper added a commit to cuviper/rust that referenced this issue Jun 1, 2017
This option forwards to each `cargo test` invocation, and applies the
same logic across all test steps to keep going after failures.  At the
end, a brief summary line reports how many commands failed, if any.

Note that if a test program fails to even start at all, or if an
auxiliary build command related to testing fails, these are still left
to stop everything right away.

Fixes rust-lang#40219.
Mark-Simulacrum added a commit to Mark-Simulacrum/rust that referenced this issue Jun 1, 2017
rustbuild: Add `./x.py test --no-fail-fast`

This option forwards to each `cargo test` invocation, and applies the
same logic across all test steps to keep going after failures.  At the
end, a brief summary line reports how many commands failed, if any.

Note that if a test program fails to even start at all, or if an
auxiliary build command related to testing fails, these are still left
to stop everything right away.

Fixes rust-lang#40219.
Mark-Simulacrum added a commit to Mark-Simulacrum/rust that referenced this issue Jun 2, 2017
rustbuild: Add `./x.py test --no-fail-fast`

This option forwards to each `cargo test` invocation, and applies the
same logic across all test steps to keep going after failures.  At the
end, a brief summary line reports how many commands failed, if any.

Note that if a test program fails to even start at all, or if an
auxiliary build command related to testing fails, these are still left
to stop everything right away.

Fixes rust-lang#40219.
cuviper added a commit to cuviper/rust that referenced this issue Jun 2, 2017
This option forwards to each `cargo test` invocation, and applies the
same logic across all test steps to keep going after failures.  At the
end, a brief summary line reports how many commands failed, if any.

Note that if a test program fails to even start at all, or if an
auxiliary build command related to testing fails, these are still left
to stop everything right away.

Fixes rust-lang#40219.
frewsxcv added a commit to frewsxcv/rust that referenced this issue Jun 3, 2017
rustbuild: Add `./x.py test --no-fail-fast`

This option forwards to each `cargo test` invocation, and applies the
same logic across all test steps to keep going after failures.  At the
end, a brief summary line reports how many commands failed, if any.

Note that if a test program fails to even start at all, or if an
auxiliary build command related to testing fails, these are still left
to stop everything right away.

Fixes rust-lang#40219.
frewsxcv added a commit to frewsxcv/rust that referenced this issue Jun 3, 2017
rustbuild: Add `./x.py test --no-fail-fast`

This option forwards to each `cargo test` invocation, and applies the
same logic across all test steps to keep going after failures.  At the
end, a brief summary line reports how many commands failed, if any.

Note that if a test program fails to even start at all, or if an
auxiliary build command related to testing fails, these are still left
to stop everything right away.

Fixes rust-lang#40219.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Projects
None yet
Development

No branches or pull requests

2 participants