Run cargo test in ci pipeline #107
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
Member
|
I think it would be better as a step after the build though. That way we avoid building the same thing twice and we also test on all targets. |
Contributor
Author
Can do. Give me a couple minutes to make an amend commit |
Speykious
approved these changes
Aug 19, 2025
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.
Looking to start contributing to this repository, noticed there were some existing unit tests that currently aren't being checked in the CI pipeline. This PR adds a workflow step to run them.
This also updates the runner for the amd64 build to be amd64 based, avoiding the need for installing a specific version of gcc and avoiding an issue with reqwest/openssl