-
Notifications
You must be signed in to change notification settings - Fork 87
Run tests against kryoptic main #328
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Jakub Jelen <[email protected]>
Fixes: parallaxsecond#311 Signed-off-by: Jakub Jelen <[email protected]>
6abd032 to
f17e54f
Compare
hug-dev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the quick fix!
wiktor-k
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks good 👌
| OUT_DIR: /__w/rust-cryptoki/kryoptic/target/debug/deps/ | ||
| RUST_BACKTRACE: 1 | ||
| run: cargo test | ||
| run: cargo build --all-features && cargo test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think check is enough, since we don't care about the output artifacts:
| run: cargo build --all-features && cargo test | |
| run: cargo check --all-features && cargo test |
The question is whether we want to check --all-targets (which include tests and examples and bins...)...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took this from ci.yml (where I probably wrote this previously). I think that just test should be enough. Not sure if we should need the check at all here as the check is executed in the other jobs (as well as the --all-targets -- the Fedora cargo should not be that much different from ubuntu cargo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point 👍
Follow-up from #311 and discussion in #326, where we agreed that keeping track of main is less problematic than keeping outdated version.