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

feature suggestion: terminate slow tests after a given deadline and regard them as failed #213

Closed
steveej opened this issue May 18, 2022 · 2 comments

Comments

@steveej
Copy link
Contributor

steveej commented May 18, 2022

without this, terminating a frozen test suite relies on an external watcher that keeps track of time. since the test harness and nextest itself already track time for each test, it would be great to have deadline support natively in the cargo stack.

for this potential feature it's actually an advantage that nextest runs each test in a separate process, because terminating processes works reliably as opposed to terminating threads which requires cooperation.

@sunshowers
Copy link
Member

Thanks for the request! Yes, I agree this makes a lot of sense.

It would be interesting to see how this interacts with #27. I guess we can apply it to the entire process.

@sunshowers
Copy link
Member

This was released as cargo-nextest 0.9.18.

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

No branches or pull requests

2 participants