-
Notifications
You must be signed in to change notification settings - Fork 105
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
Issue injecting Kani module to dependency (zerocopy) #3238
Comments
This might be the same problem as #3101. We are investigating. |
I believe the (pending) fix for #3101 also addresses the Kani issue here, but then I actually get build failures unrelated to Kani on this project (when building the |
We want to run the proofs in the target crate and don't need to build (or run) the proofs in any of the host crates. This avoids a need to make available the `kani` crate to any such host crates. Resolves model-checking#3101, model-checking#3238
I tried too, I think this is given by the version of rust compiler used by Kani! A quick check with |
Fixed by #3244. |
If you're up for building the the latest version of kani: we now have both the fix from #3244 merged as well as a more recent toolchain/rust compiler, which might fix those problems. |
@tautschnig I saw that the build chain can be easily replaced while compiling locally. I'm just curious why Kani sticks so quickly with nightly releases. |
I tried to just create a basic proof on the Aptos-Core project, but I faced an issue with building with Kani, likely a bug with module injection:
I believe this bug triggers only on certain combination of features, cargo build environment, and previous issue: #3109, where there was some issue with replicating the environment.
I tried this code:
git clone https://github.com/aptos-labs/aptos-core
./scripts/dev_setup.sh
consensus/src/transaction_shuffler/sender_aware.rs
cargo kani --package aptos-consensus --harness transaction_shuffler::sender_aware::verification::test_3_sender_shuffling
with Kani version: 0.52
I expected to see this happen: Kani building the project.
Instead, this happened: A dependency which uses Kani, zerocopy, fails to build because there is a missing Kani module.
The text was updated successfully, but these errors were encountered: