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
I find that when using -C opt-level=0 as the compilation optimization level, all of the test cases can pass. However, if we use -C opt-level=1/2/3/s/z, an error would be triggered.
For example, using the command:
RUSTFLAGS="-Z mir-opt-level=0 -C opt-level=1" cargo test
The output is as below:
Running tests/flatten.rs (target/debug/deps/flatten-01ee475df42d1a15)
running 6 tests
error: The argument '<arg>' was provided more than once, but cannot be used multiple times
USAGE:
test <arg>
For more information try --help
error: test failed, to rerun pass `--test flatten`
Caused by:
process didn't exit successfully: `/local/home/zixliu/crates/structopt/target/debug/deps/flatten-01ee475df42d1a15` (exit status: 1)
note: test exited abnormally; to see the full output pass --nocapture to the harness.
The text was updated successfully, but these errors were encountered:
This isn't a bug. The panic comes from clap here and only happens when debug assertions are enabled. When they aren't enabled, the code proceeds to the alternative error path which calls std::process::exit.
tamird
added a commit
to tamird/structopt
that referenced
this issue
Sep 30, 2024
I find that when using
-C opt-level=0
as the compilation optimization level, all of the test cases can pass. However, if we use-C opt-level=1/2/3/s/z
, an error would be triggered.For example, using the command:
The output is as below:
The text was updated successfully, but these errors were encountered: