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

--failed flag for x test #114609

Closed
1 of 4 tasks
darklyspaced opened this issue Aug 8, 2023 · 4 comments
Closed
1 of 4 tasks

--failed flag for x test #114609

darklyspaced opened this issue Aug 8, 2023 · 4 comments
Assignees
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc C-feature-request Category: A feature request, i.e: not implemented / a PR. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Comments

@darklyspaced
Copy link
Contributor

darklyspaced commented Aug 8, 2023

I'm proposing a flag for x test called --failed that reruns all tests that failed the last time that they were ran.

Of course, this would require the tool to keep track of the status of different tests -- not run, passed, failed etc -- in a permanent file. However, by doing this, we could also potentially add an optional pre-push hook that checks whether there are any tests that are failing and prompts the user to rerun those tests before pushing.

We could also integrate the tool with x suggest so that this is an option that is suggested and executed when there are tests that were failed on the previous iteration. I have started brewing up a PR implementing this feature; I wanted to get some feedback on whether this is something that people would actually find useful (I certainly would!).

cc @Ezrashaw (you might be interested based off your work on x suggest)

Tasks

  1. S-blocked T-bootstrap
    onur-ozkan
@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Aug 8, 2023
@Noratrieb Noratrieb added A-testsuite Area: The testsuite used to check the correctness of rustc T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) C-feature-request Category: A feature request, i.e: not implemented / a PR. and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Aug 8, 2023
@chenyukang
Copy link
Member

For most cases, I use option --only-modified to only run test cases which modified in local, it's useful if the cmp or code in test case changed.
--failed option may cover more scenarios such as crash happened in testing.

@darklyspaced
Copy link
Contributor Author

@rustbot claim

@darklyspaced
Copy link
Contributor Author

darklyspaced commented Aug 14, 2023

Discussion about the feature addition on Zulip

@onur-ozkan
Copy link
Member

During the Bootstrap team meeting, we decided that this feature is not necessary. The reason is that the Bootstrap layer is already complex and large, and we believe that the maintenance effort required for this feature wouldn't justify the benefit it would bring.

Thank you for your proposal!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc C-feature-request Category: A feature request, i.e: not implemented / a PR. 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

5 participants