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

Consider switching to nextest #338

Closed
joepio opened this issue Mar 23, 2022 · 1 comment · Fixed by #339
Closed

Consider switching to nextest #338

joepio opened this issue Mar 23, 2022 · 1 comment · Fixed by #339

Comments

@joepio
Copy link
Member

joepio commented Mar 23, 2022

Seems to be a good alternative to cargo test. Faster, detect flaky tests (e.g. #320).

@joepio
Copy link
Member Author

joepio commented Mar 23, 2022

Yup, it's great.

@joepio joepio closed this as completed Mar 23, 2022
joepio added a commit that referenced this issue Mar 23, 2022
* #337 code coverage in contribute, action script #338 try nextest

* #337 use nightly for coverage

* #337 llvm-tools

* #338 random_string fix test, add retries

* #337 gtk in codecov

* #340 playwright
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

Successfully merging a pull request may close this issue.

1 participant