Your message dated Fri, 5 Jan 2024 07:11:06 -0500
with message-id
<caj0cceyhog58y+rwq9cab+45bud7yxkqjajnka-nir+avo7...@mail.gmail.com>
and subject line Fixed in 0.11.0-2
has caused the Debian Bug report #1056031,
regarding rust-rstest-test: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rstest-test
Version: 0.11.0-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rstest-test/39198638/log.gz
...
84s ---- more_tests::case_2_contains stdout ----
84s Stderr: debian cargo wrapper: options, profiles, parallel: ['parallel=64']
[] ['-j64']
84s debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
84s debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '+stable', '-Zavoid-dev-deps', 'test', '--verbose',
'--verbose', '-j64', '--target', 'x86_64-unknown-linux-gnu'],) {}
84s error: no such subcommand: `+stable`
84s
84s Cargo does not handle `+toolchain` directives.
84s Did you mean to invoke `cargo` through `rustup` instead?
84s
84s thread 'more_tests::case_2_contains' panicked at 'Empty stdout!',
/usr/share/cargo/registry/rstest-test-0.11.0/src/utils.rs:308:13
84s stack backtrace:
84s 0: std::panicking::begin_panic
84s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:610:12
84s 1: rstest_test::utils::TestResults<S>::assert
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/src/utils.rs:308:13
84s 2: framework::more_tests
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:87:5
84s 3: framework::more_tests::case_2_contains
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:58:1
84s 4: framework::more_tests::case_2_contains::{{closure}}
84s at
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:58:1
84s 5: core::ops::function::FnOnce::call_once
84s at
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
84s 6: core::ops::function::FnOnce::call_once
84s at
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
84s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
84s
84s
84s failures:
84s add_local_dependency
84s more_tests::case_1_default_conf
84s more_tests::case_2_contains
84s nocapture_in_tests
84s one_fail::case_1_default_conf
84s one_fail::case_2_contains
84s one_success::case_1_default_conf
84s one_success::case_2_contains
84s should_check_just_contains_conf
84s should_check_just_contains_on_some_test
84s should_check_some_tests_as_contains
84s should_detect_wrong_contains
84s tests_with_should_panic::case_1_default_conf
84s tests_with_should_panic::case_2_contains
84s
84s test result: FAILED. 1 passed; 14 failed; 0 ignored; 0 measured; 0
filtered out; finished in 0.79s
84s
84s error: test failed, to rerun pass `--test framework`
85s autopkgtest [21:27:08]: test librust-rstest-test-dev::
-----------------------]
85s autopkgtest [21:27:08]: test librust-rstest-test-dev:: - - - - - - - - -
- results - - - - - - - - - -
85s librust-rstest-test-dev: FAIL non-zero exit status 101
85s autopkgtest [21:27:08]: @@@@@@@@@@@@@@@@@@@@ summary
85s rust-rstest-test:@ FAIL non-zero exit status 101
85s librust-rstest-test-dev:default FAIL non-zero exit status 101
85s librust-rstest-test-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Version: 0.11.0-2
I've fixed the test suite in version 0.11.0-2. package is now in unstable
--
regards,
Reinhard
--- End Message ---
