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 20240429-2+py315.1.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
tests ran 3.14

Rebuilding it releases 1 package waiting on it, as this stage last counted.

What was sent

published, 20240429-2+py315.1.

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.14
the harness that ran them not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
20240429-2+py315.1 arm64 test fail rebuilt 3.14 ok 2026-08-02 18:56
20240429-2+py315.1 amd64 test fail rebuilt 3.14 ok 2026-08-02 19:53
20240429-2 arm64 test fail the archive's (reference arm) named none 2026-08-02 15:26
20240429-2 amd64 test fail the archive's (reference arm) named none 2026-08-02 15:26