Skip to content

Add a flag to compiletest to control whether it should fail fast or not #2144

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.

Sign up for GitHub

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

Jump to bottom
Closed
celinval opened this issue Jan 23, 2023 · 0 comments · Fixed by #2145
Closed

Add a flag to compiletest to control whether it should fail fast or not #2144

celinval opened this issue Jan 23, 2023 · 0 comments · Fixed by #2145
Assignees
@celinval
Labels
[C] Internal Tracks some internal work. I.e.: Users should not be affected.

Comments

@celinval
Copy link
Contributor

Proposed change: Add a --no-fail-fast to compiletest which will execute the entire suite regardless of failure.

Motivation: This used to be the default behavior but it has changed to always failing fast after #2045. I think both modes are useful, but for CI I would prefer printing all failures in the suite before aborting. The more information the better.
@celinval celinval added the [C] Internal Tracks some internal work. I.e.: Users should not be affected. label Jan 23, 2023
@celinval celinval self-assigned this Jan 23, 2023
@celinval celinval mentioned this issue Jan 23, 2023
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@celinval celinval

Labels
[C] Internal Tracks some internal work. I.e.: Users should not be affected.
Projects
No open projects
Kani 2023-02-13
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add --no-fail-fast to compiletest celinval/kani-dev
1 participant
@celinval