-
Notifications
You must be signed in to change notification settings - Fork 346
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
turn on musl test in CI #2069
turn on musl test in CI #2069
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2069 +/- ##
=======================================
Coverage 64.81% 64.81%
=======================================
Files 129 129
Lines 14768 14768
=======================================
Hits 9572 9572
Misses 5196 5196 |
Signed-off-by: yihuaf <yihuaf@unkies.org>
|
||
# run cargo unittests | ||
unittest: | ||
cd ./crates | ||
LD_LIBRARY_PATH=${HOME}/.wasmedge/lib cargo test --all --all-targets --all-features | ||
|
||
# run permutated feature compilation tests | ||
featuretest: | ||
test-features: |
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.
👍
.github/workflows/main.yml
Outdated
# The `setup-rust-toolchain` action will always choose toolchain file with | ||
# no way to override. | ||
- name: Setup Rust toolchain and cache | ||
uses: dtolnay/rust-toolchain@stable |
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.
Do we need to specify stable
? I wonder because we have had rust-toolchain.toml
.
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 catch! I mis-read the documentation and thought the stable
referred to the github action version... I will make the change.
Signed-off-by: yihuaf <yihuaf@unkies.org>
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.
🚀
Turn the musl target testing in CI. At the moment, this is only for
libcontainer
since there is an actual usecase fromaurae
project to compile libcontainer statically withmusl
. I choose to put the musl in a separate job because of the unique requirement for the nightly toolchain. While it is easy for us to switch toolchains in the dev box, it proves to be not possible to mix toolchains with the existing rust github action setup. It is easier to create a new job with the specific toolchains required.