<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Package: rust-csv<br>
Version: 1.1.5-2<br>
Severity: serious<br>
<br>
rust-csv's autopkgtest is failing, which is blocking it's
migration to testing.<br>
<br>
<blockquote type="cite">
<pre>--- 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.</pre>
</blockquote>
Doing some experiments running the tests manually, it appears the
culprit is the "--all-targets" option<br>
passed to cargo test by the autopkgtests. This seems to stop cargo
from building the examples in a<br>
runnable form.<br>
<br>
I'm not sure what the best way forward here is, one could override
debian/tests/control, but experiance<br>
shows that is a maintinance burden, because debian/tests/control
hardcodes the crate version.<br>
<br>
The other option would be to just disable the tests in question.
Not ideal but probablly not a disaster<br>
either.<br>
<br>
Does anyone have any better ideas?<br>
<br>
</p>
</body>
</html>