-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat(ci): add rv32im compilation checks #12925
Conversation
.github/assets/check_rv32im.sh
Outdated
# Array of crates to exclude | ||
# Used with the `contains` function. | ||
# shellcheck disable=SC2034 | ||
exclude_crates=( |
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.
can we invert this please,
checking crates for inclusion is pretty annoying, because what we need to do here now is check that a selection of crates compiles for this target, then we don't need the cargo metadata call
.github/assets/check_rv32imac.sh
Outdated
reth-evm | ||
reth-primitives | ||
reth-primitives-traits | ||
reth-optimism-forks | ||
reth-optimism-chainspec |
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.
this will take a while until we support all of those, can we start with the one that currently succeeds and comment out the others, otherwise this pr will be open for a while
reth-codecs-derive | ||
# reth-evm | ||
# reth-primitives | ||
# reth-primitives-traits |
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.
this we should target next
addresses #12891
adds a ci workflow to check that all expected crates are able to compile to the
riscv32imac
target. this is helpful for FPVM / ZK teams to know which crates are safe to import directly from reth.