-
Notifications
You must be signed in to change notification settings - Fork 0
Feat: Support kani harnesses from crates beyond libcore #122
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It depends on verify-rust-std project to include what crates need to verify by kani.
[src/bin/distributed-verification/functions/mod.rs:21:5] cap = 31666 [src/bin/distributed-verification/functions/mod.rs:21:5] rustc_public::local_crate().name = "core" Compiling alloc v0.0.0 (/home/gh-zjp-CN/distributed-verification/verify-rust-std/library/alloc) [src/bin/distributed-verification/functions/mod.rs:21:5] cap = 2817 [src/bin/distributed-verification/functions/mod.rs:21:5] rustc_public::local_crate().name = "alloc" Compiling dummy-crate v0.1.0 (/home/gh-zjp-CN/distributed-verification/tests/dummy-crate) [src/bin/distributed-verification/functions/mod.rs:21:5] cap = 1 [src/bin/distributed-verification/functions/mod.rs:21:5] rustc_public::local_crate().name = "dummy_crate" Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 25s crate = alloc Functions = 3107 Proofs = 2 crate = core Functions = 32034 Proofs = 1366 crate = dummy_crate Functions = 1 Proofs = 0 Total Proofs = 1368 Total Functions = 35142
$ ls assets/json/ alloc.json core.json dummy_crate.json proc_macro2.json rustflags.json
{ "crate": "core", "file": "core/src/alloc/layout.rs", "func": "<alloc::layout::Layout as clone::Clone>::clone", "hash": "138669527279575425473478508059426767195" }
to solve thread 'main' (23372) panicked at src/bin/verify_rust_std/env.rs:41:5: OUTPUT_DIR="/home/runner/work/distributed-verification/distributed-verification/assets/json" doesn't point to a valid path.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
verify_rust_std merge --hash-json
now accepts a path pointing to a folder or a json file: when it's a folder, read all json files, but silent if json is not properly deserializedassets/json
with name beingcrate_name.json