Package: rust-csv
Version: 1.1.5-2
Severity: serious
rust-csv's autopkgtest is failing, which is blocking it's migration to
testing.
--- cookbook_read_basic stdout ----
thread 'cookbook_read_basic' panicked at 'command spawns successfully: Os { code: 2,
kind: NotFound, message: "No such file or directory" }', tests/tests.rs:412:33
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.56.0/library/std/src/panicking.rs:517:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.56.0/library/core/src/panicking.rs:101:14
2: core::result::unwrap_failed
at /usr/src/rustc-1.56.0/library/core/src/result.rs:1617:5
3: core::result::Result<T,E>::expect
at /usr/src/rustc-1.56.0/library/core/src/result.rs:1259:23
4: tests::cmd_output_with
at ./tests/tests.rs:412:21
5: tests::cookbook_read_basic
at ./tests/tests.rs:27:15
6: tests::cookbook_read_basic::{{closure}}
at ./tests/tests.rs:25:1
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.56.0/library/core/src/ops/function.rs:227:5
8: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.56.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
Doing some experiments running the tests manually, it appears the
culprit is the "--all-targets" option
passed to cargo test by the autopkgtests. This seems to stop cargo from
building the examples in a
runnable form.
I'm not sure what the best way forward here is, one could override
debian/tests/control, but experiance
shows that is a maintinance burden, because debian/tests/control
hardcodes the crate version.
The other option would be to just disable the tests in question. Not
ideal but probablly not a disaster
either.
Does anyone have any better ideas?
