Shortcuts

/
focus the search box
Escape
leave the search, or close a menu or this
r
cycle the refresh interval
t
cycle the theme
?
this list

Where it stands

tests failed, ours is 0.6-42-ga14256a-0.3+py315.1.

Nothing recorded is waiting on this one.

What was sent

published, 0.6-42-ga14256a-0.3+py315.1.

What is known

QuestionAnswerSaid byAs of
does the release team track this? dependency level 0
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong.
amd64 bad, arm64 bad, armhf bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad
release.debian.org, from their ben tracker 2026-09-16 04:49 UTC
Is this filed in Debian? #1144788
Filed by this round, or adopted from the BTS by its usertag.
the tracker's own record not dated
has anybody reported this under the usertag? 1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks
#1144788 iotop: autopkgtest fails under incus-lxc: Netlink error: Operation not permitted (1)
the BTS usertag not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
0.6-42-ga14256a-0.3+py315.1 arm64 test fail rebuilt named none ok 2026-08-02 18:43
0.6-42-ga14256a-0.3+py315.1 amd64 test fail rebuilt named none ok 2026-08-02 19:34
0.6-42-ga14256a-0.3 arm64 test fail the archive's (reference arm) named none 2026-08-02 15:26
0.6-42-ga14256a-0.3 amd64 test fail the archive's (reference arm) named none 2026-08-02 15:26