Closed est31 closed 1 year ago
Also, FTR, this is the reason why I've held back a release of cargo-udeps since, because I don't know how widespread the regression is.
The issue seems to be that cargo does not interpret the cli arguments of the subcommand any more.
On 19ecf744290cea3f9e2459d249b683802d086c36:
info: filter: Only { all_targets: true, lib: Default, bins: All, examples: All, tests: All, benches: All }
On master:
info: filter: Default { required_features_filterable: true }
(When you do cargo +nightly test --all --no-fail-fast --test normal-dev-build with_all_target
, and add a line config.shell().info(format_args!("filter: {:?}", compile_opts.filter))?;
to OptUdeps::run
, plus change stderr = Shell::from_write(Box::new(vec![]))
to stderr = Shell::new()
in Runner::run
for printing).
Workaround applied in 0d4889b18b9fa743c6618bf76d116fa39537606e. Upstream issue filed: https://github.com/clap-rs/clap/issues/4869
Since the update of cargo to 0.66 in a103529deb0161305085bdc87f8ee163483a123c , there have been two regressions. One was fixed by a14f2a78a3be935ff681fa0eacb0d04ca7b24d82, but the second is still around:
Through a git bisect of cargo, I've traced this down to the clap upgrade of cargo, that means any commit before works, any commit after doesn't. Also, the issue has nothing to do with the rustc used, as both the older and newer rustc work. I'm filing this issue to collect more information about the regression.