Your message dated Tue, 15 Apr 2025 15:20:16 +0000
with message-id <[email protected]>
and subject line Bug#1102198: fixed in rust-dirty-tracker 0.3.0-4
has caused the Debian Bug report #1102198,
regarding rust-dirty-tracker: flaky autopkgtest
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 [email protected]
immediately.)
--
1102198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102198
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-dirty-tracker
Version: 0.3.0-3
Severity: serious
X-Debbugs-Cc: [email protected]
Dear maintainer,
the autopkgtests of rust-dirty-tracker are flaky:
https://ci.debian.net/packages/r/rust-dirty-tracker/testing/amd64/59604769/
test tests::test_create_and_follow_subdir ... FAILED
failures:
---- tests::test_create_and_follow_subdir stdout ----
thread 'tests::test_create_and_follow_subdir' panicked at src/lib.rs:304:9:
assertion `left == right` failed
left: {"/tmp/.tmpHcqmU8/subdir"}
right: {"/tmp/.tmpHcqmU8/subdir", "/tmp/.tmpHcqmU8/subdir/file"}
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.85.0/library/std/src/panicking.rs:692:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:75:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:364:5
4: dirty_tracker::tests::wait_for
at ./src/lib.rs:304:9
5: dirty_tracker::tests::test_create_and_follow_subdir
at ./src/lib.rs:501:9
6: dirty_tracker::tests::test_create_and_follow_subdir::{{closure}}
at ./src/lib.rs:481:39
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
8: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
tests::test_create_and_follow_subdir
test result: FAILED. 9 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.07s
error: test failed, to rerun pass `--lib`
autopkgtest [16:45:57]: test librust-dirty-tracker-dev::
-----------------------]
Other recent failures include
https://ci.debian.net/packages/r/rust-dirty-tracker/testing/amd64/58291451/
and
https://ci.debian.net/packages/r/rust-dirty-tracker/testing/amd64/58047631/.
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: rust-dirty-tracker
Source-Version: 0.3.0-4
Done: Peter Michael Green <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rust-dirty-tracker, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green <[email protected]> (supplier of updated
rust-dirty-tracker package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 15 Apr 2025 14:56:32 +0000
Source: rust-dirty-tracker
Architecture: source
Version: 0.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
<[email protected]>
Changed-By: Peter Michael Green <[email protected]>
Closes: 1102198
Changes:
rust-dirty-tracker (0.3.0-4) unstable; urgency=medium
.
* Team upload.
* Package dirty-tracker 0.3.0 from crates.io using debcargo 2.7.8
* Skip test_create_and_follow_subdir on remaining architectures, it seems
to be generally flaky (Closes: #1102198).
Checksums-Sha1:
6f3de6e0fcf91cb8258d81d1a66d31191e5a717b 2428 rust-dirty-tracker_0.3.0-4.dsc
adfd0c0c85afbe33d4819331199674ce4dda4e58 2464
rust-dirty-tracker_0.3.0-4.debian.tar.xz
43aa0beee28369f3048512d2185036fbdfe80163 8539
rust-dirty-tracker_0.3.0-4_source.buildinfo
Checksums-Sha256:
12bdbb6fcb18587b5610450e11822ebdee0b336d70354217c3f312eaaea7ad8a 2428
rust-dirty-tracker_0.3.0-4.dsc
c95ff2cf471d640decb42f341c559fbd80175f7df9e513912b063ec29107de6e 2464
rust-dirty-tracker_0.3.0-4.debian.tar.xz
a6b00faee33c0a94692abc3827b51e1868202f7ca940c6bf18046794eacbe6ab 8539
rust-dirty-tracker_0.3.0-4_source.buildinfo
Files:
6c3ba799c7341a43e5ee7a643116679d 2428 rust optional
rust-dirty-tracker_0.3.0-4.dsc
0414975c035a5b0e8acd3b16d082aabf 2464 rust optional
rust-dirty-tracker_0.3.0-4.debian.tar.xz
7022112489295698c1a98b790212fc1a 8539 rust optional
rust-dirty-tracker_0.3.0-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmf+c8EUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xsdjg/9GXeOcsfNB9eZzIP/b94AKml7qvtW
V/Ho4ByjHY5ZX3iOFQBIxsvlMooOa8+CYm/S0nmvJgFyWaJaQXgyd4H4rIdJmsm/
iIY70JSOrJRBFSiATamj5oMMJtgOseGv9Fzek1aAvpXV57yXYHq8a7h7pdGnHKxH
ij67vp555c79O1jlNXK5TTPj5l7rwXPzB7y1DSlxhLKcDDZpRiS9HctVwqN2kGNr
3y5T6mqOaykyPixlnIseuyVaJmszyxVQG5c1EBOEtgjDmcTt+usEtr6HsPUgik31
RA50UKIX5uppr6zR3/7FG8iqjWrVSSodxUA+MU6XHam2x9aovjWn0T0oX7K+o6Pn
xGGkQY3DFrg+Brb3TvSvcJ5Z4iGwQ9deTa7GktVYkkvzbDspWrSKDKxTMNeilxs9
y8B5l2Ay7clnCDzPXrmam/S9YVZHyXmK7MfG+5p4JBsvmHnaqbpIzLylba0XIGeS
GK5c59rJmuf2JtFEPalLWmmTrBdkeclPbx3beSgf2ikd6nBsyyc/BX7UW245n966
QC/SsCQlSjuxoEm//clI3nS/d59+H88o4X4wXlEX3PWp13IiljqJbxoti38coXi4
/li+njsDt/1apK/9kdfE6wqpZjVO8KQjNn37B6i8tdM2QVjKCGBQsV+48mvhg4S6
d8/encngct09i/I=
=+PFP
-----END PGP SIGNATURE-----
pgpGNBv4_nLOo.pgp
Description: PGP signature
--- End Message ---
