Improve CI job for running tests #234
Merged
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
Adapted the execution of cargo nextest to use a CI specific profile and produce test results in JUnit format. Included the running of the doctests in the same job that runs cargo nextest so that the doctests are also executed for all relevant feature combinations. Merged the test results into a single archive so that all results are part of the archive that is attached to releases.
sophokles73
force-pushed
the
add_nextest_configuration
branch
from
c6ccf1a to
110da24
Compare
| name: test-results | ||
| path: testresults--all-features.json | ||
|
|
||
| # [impl->req~up-language-ci-test~1] |
Contributor
There was a problem hiding this comment.
In this scenario, where did you move the req implementation marker?
Contributor
Author
There was a problem hiding this comment.
It is already on the nextest job which now also includes running the doctests ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adapted the execution of cargo nextest to use a CI specific profile and
produce test results in JUnit format.
Included the running of the doctests in the same job that runs cargo
nextest so that the doctests are also executed for all relevant
feature combinations.
Merged the test results into a single archive so that all results are
part of the archive that is attached to releases.