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

← In progress

Where it stands

tests failed, ours is 4.16.4.1-6+py315.1.
archive has moved on; rebuild before believing this
tests ran 3.13
a retest under this interpreter would settle it

Nothing recorded is waiting on this one.

What was sent

published, 4.16.4.1-7+py315.1, as work request 1291092.

Sent before this one: 4.16.4.1-6+py315.1. A version that was sent is spent, whatever came of it.

What is known

QuestionAnswerSaid byAs of
does Debian's own test suite pass? not tested by debian
Debian runs no autopkgtest for this, so we have no independent baseline: nothing here distinguishes a failure this interpreter caused from one the package always had
ci.debian.net not dated
did its tests run this interpreter? others only
Its tests named the interpreters they ran and ours was not among them, so whatever they say is about those. A census blocker explains most of them: the package builds against whatever `python3-dev` points at. Without one, a retest under this interpreter would settle it.
ran 3.13
the harness that ran them not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
4.16.4.1-6+py315.1 amd64 test fail rebuilt 3.13 2026-08-18 10:59
4.16.4.1-6 amd64 test fail the archive's (reference arm) 3.13 2026-08-18 09:27
4.16.4.1-6+py315.1 all build pass unknown not read yet 2026-08-18 10:58