You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and adapting my code according to the API changes,
cargo build works
cargo wasm works
cargo unit-test fails to compile with
$ cargo unit-test
Compiling dynasm v0.5.2
Compiling wasmer-clif-fork-frontend v0.44.0
Compiling cranelift-native v0.44.0
Compiling wasmer-clif-fork-wasm v0.44.0
error[E0554]: `#![feature]` may not be used on the stable release channel
--> /myhome/.cargo/registry/src/github.com-1ecc6299db9ec823/dynasm-0.5.2/src/lib.rs:1:1
|
1 | #![feature(proc_macro_diagnostic)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error[E0554]: `#![feature]` may not be used on the stable release channel
--> /myhome/.cargo/registry/src/github.com-1ecc6299db9ec823/dynasm-0.5.2/src/lib.rs:2:1
|
2 | #![feature(proc_macro_span)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Compiling wasmer-clif-backend v0.11.0
Compiling wasmer-runtime v0.11.0
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0554`.
error: could not compile `dynasm`.
Yeah, singlepass is the default for the production vm (gas metering), but I swap the defaults in the contracts for easier testing on stable. Gas metering is only a secondary concern there.
After upgrading cosmwasm and cosmwasm-vm in my contract with
and adapting my code according to the API changes,
cargo build
workscargo wasm
workscargo unit-test
fails to compile withwhere dynasm is known to work on rust nightly only.
There are two things I wonder:
dynasm
andwasmer-singlepass-backend
entries inerc20/Cargo.lock
did not change.cosmwasm_vm
is only used for integration tests. Why does the commandcargo unit-test
even need to compile it?The text was updated successfully, but these errors were encountered: