Skip to content

rustbuild: Add ./x.py test --no-fail-fast - #42363

Merged
bors merged 1 commit into
rust-lang:masterfrom
cuviper:no-fail-fast
Jun 3, 2017
Merged

bors merged 1 commit into
rust-lang:masterfrom
cuviper:no-fail-fast

Conversation

@cuviper

@cuviper cuviper commented Jun 1, 2017 •

Copy link
Copy Markdown
Member

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 #40219.

@rust-highfive

Copy link
Copy Markdown
Contributor

r? @aturon

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

@Mark-Simulacrum

Copy link
Copy Markdown
Member

r? @alexcrichton

@alexcrichton

Copy link
Copy Markdown
Member

Thanks! I've personally held off on doing this in the past b/c I was hoping to add a general "keep going" flag but that'd require keeping track of dependencies between stages and likely changing everything to return Result. This, however, seems like a pragmatic and simple implementation that solves the real problem which comes up, running all tests despite failures happening.

In other words, looks great!

@bors: r+

@bors

bors commented Jun 1, 2017

Copy link
Copy Markdown
Collaborator

📌 Commit 4880ae8 has been approved by alexcrichton

@Mark-Simulacrum

Copy link
Copy Markdown
Member

@bors rollup

Mark-Simulacrum added a commit to Mark-Simulacrum/rust that referenced this pull request 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 pull request 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.
@bors

bors commented Jun 2, 2017

Copy link
Copy Markdown
Collaborator

☔ The latest upstream changes (presumably #42128) made this pull request unmergeable. Please resolve the merge conflicts.

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

cuviper commented Jun 2, 2017

Copy link
Copy Markdown
Member Author

Rebased. I had to add a try_run_quiet variant too.

@Mark-Simulacrum

Copy link
Copy Markdown
Member

@bors r=alexcrichton

@bors

bors commented Jun 2, 2017

Copy link
Copy Markdown
Collaborator

📌 Commit 617aea4 has been approved by alexcrichton

@shepmaster shepmaster added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Jun 2, 2017
frewsxcv added a commit to frewsxcv/rust that referenced this pull request 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 pull request 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.
bors added a commit that referenced this pull request Jun 3, 2017
Rollup of 5 pull requests

- Successful merges: #42353, #42354, #42363, #42368, #42382
- Failed merges:
@bors
bors merged commit 617aea4 into rust-lang:master Jun 3, 2017
@cuviper
cuviper deleted the no-fail-fast branch September 26, 2017 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants