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

CI: check no-std support #56

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

japaric
Copy link
Contributor

@japaric japaric commented Nov 27, 2023

for the time being, this only checks that the hpke-rs-crypto crate is no-std compatible.

this new CI job won't pass until #50 is merged

Copy link
Member

@franziskuskiefer franziskuskiefer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with one nit

toolchain: stable
target: thumbv7em-none-eabihf
default: true
- name: Fuzz Base w/ RustCrypto
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like a c&p . How about something like this?

Suggested change
- name: Fuzz Base w/ RustCrypto
- name: Build no-std w/ RustCrypto

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for catching that

@japaric
Copy link
Contributor Author

japaric commented Nov 29, 2023

I've updated the PR to check that all the crates (minus the evercrypt one) have proper no-std support.

Copy link
Member

@franziskuskiefer franziskuskiefer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks!

@franziskuskiefer franziskuskiefer merged commit e56ea4a into cryspen:main Nov 29, 2023
14 of 15 checks passed
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 this pull request may close these issues.

2 participants