ci: Do not use nextest #6266
Open
ci: Do not use nextest #6266
+11
−63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lutter
force-pushed
the
lutter/no-nextest
branch
2 times, most recently
from
cf4c81f to
d106ebb
Compare
Nextest's process-per-test model is not well suited for how our tests work since it requires that database connectiosn are set up for every test in a test suite, rather than just once per suite.
lutter
force-pushed
the
lutter/no-nextest
branch
from
d106ebb to
67b6e24
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nextest's process-per-test model is not well suited for how our tests work since it requires that database connectiosn are set up for every test in a test suite, rather than just once per suite. Running tests with nextest is actually quite a bit slower than just using
cargo test