Incorrect error handling for processes that fail to spawn on windows #1778
Labels
O-windows
Operating system: Windows
Milestone
Comments
nikomatsakis
pushed a commit
to nikomatsakis/rust
that referenced
this issue
Mar 21, 2012
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
Users can now select a subset of harnesses to run using `--harness` multiple times. Previously users could either run a single harness or they had to run them all. For the example provided in rust-lang#1778: ```rust // example.rs #[kani::proof] fn a() {} #[kani::proof] fn b() {} #[kani::proof] fn c() {std::unimplemented!();} ``` Users can select harnesses `a` and `b` by running: ```bash $ kani example.rs --harness a --harness b ``` In case of multiple matches, Kani will run all harnesses that matches at least one of the `--harness` argument.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Described in #1722, on the windows build (at least) rustc has been hanging when various sub-utilities (like rm) are not available on the PATH.
The text was updated successfully, but these errors were encountered: