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
The instructions for the concrete playback feature mention that once a concrete playback test is generated, one can run it with cargo test. For packages that pin a specific rust toolchain (e.g. via a rust-toolchain file), this could result in an error if the pinned rust toolchain is a stable release because compiling Kani requires using nightly due to the usage of unstable features.
cargo kani --harness main --enable-unstable --concrete-playback=inplace
Run cargo test kani_concrete_playback_main_241008145652399799 to run the concrete trace. This errors out with:
Compiling conc_playback v0.1.0 (/home/ubuntu/examples/new-iss8/conc_playback)
Compiling quote v1.0.21
Compiling syn v1.0.99
Compiling kani_macros v0.9.0 (https://github.com/model-checking/kani#6405617b)
Compiling kani v0.9.0 (https://github.com/model-checking/kani#6405617b)
error[E0554]: `#![feature]` may not be used on the stable release channel
--> /home/ubuntu/.cargo/git/checkouts/kani-0ce0dacf5e98886d/6405617/library/kani/src/lib.rs:5:1
|
5 |#![feature(rustc_attrs)]| ^^^^^^^^^^^^^^^^^^^^^^^^
For more information about this error, try `rustc --explain E0554`.
error: could not compile `kani` due to previous error
The text was updated successfully, but these errors were encountered:
The instructions for the concrete playback feature mention that once a concrete playback test is generated, one can run it with
cargo test
. For packages that pin a specific rust toolchain (e.g. via arust-toolchain
file), this could result in an error if the pinned rust toolchain is a stable release because compiling Kani requires using nightly due to the usage of unstable features.Steps to reproduce:
cargo new --lib conc_playback
cd conc_playback
Cargo.toml
:src/lib.rs
with the following:cargo test kani_concrete_playback_main_241008145652399799
to run the concrete trace. This errors out with:The text was updated successfully, but these errors were encountered: