action needed
Debci reports failed tests
high
-
unstable: fail (log)
The tests ran in 0:03:31
Last run: 2026-05-25T04:33:11.000Z
Previous status: unknown
-
testing: fail (log)
The tests ran in 0:06:10
Last run: 2026-08-01T13:37:15.000Z
Previous status: unknown
-
stable: pass (log)
The tests ran in 0:02:52
Last run: 2026-07-18T01:43:36.000Z
Previous status: unknown
testing migrations
-
excuses:
- Migration status for rust-maybe-async (0.2.7-1 to 0.2.11-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- ∙ ∙ Missing build on riscv64
- ∙ ∙ Autopkgtest for rust-gix-protocol/0.61.0-2: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for rust-maybe-async/0.2.11-1: amd64: Test triggered, arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Lintian check waiting for test results on riscv64 - info
- ∙ ∙ Reproducibility check waiting for results on i386 - info
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-maybe-async.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/r/rust-maybe-async.png){kind=link}