-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
make wasm run in ci again #185
base: main
Are you sure you want to change the base?
Conversation
@@ -8,6 +8,6 @@ | |||
rustflags = ["-Ctarget-cpu=native"] | |||
rustdocflags = ["-Ctarget-cpu=native"] | |||
|
|||
[target.wasm32-wasi] | |||
[target.wasm32-wasip1] |
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.
You probably need to have the same target config for both in case you want to test the MSRV still. Ideally with a comment to note that it can be removed once the MSRV is 1.81+ or so.
.github/workflows/rust.yml
Outdated
- { target: wasm32-wasip1, toolchain: "1.61", os: ubuntu-latest, wasmtime: v5.0.0 } | ||
- { target: wasm32-wasip1, toolchain: stable, os: ubuntu-latest, wasmtime: v5.0.0 } |
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.
Here without p1 now (only on 1.61 of course).
Is that something we can fix here or should we adjust the CI flow to bypass it and file an issue with rust-lang/rust? |
Why would we file an issue upstream? You just need to pass the new P1 env vars as well, which should be |
No description provided.