Source: rust-dirty-tracker
Version: 0.3.0-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
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

Reply via email to