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

built, ours is 0.75.0-1+py315.1, waiting on libsolv, rpm.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
tests ran 3.14

Nothing recorded is waiting on this one.

What was sent

published, 0.75.0-1+py315.1, as work request 1016434.

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
0.75.0-1+py315.1 arm64 test pass rebuilt 3.14 2026-08-17 12:05
0.75.0-1+py315.1 amd64 test pass rebuilt 3.14 2026-08-17 12:03
0.75.0-1 arm64 test fail the archive's (reference arm) named none 2026-08-17 12:00
0.75.0-1 amd64 test fail the archive's (reference arm) named none 2026-08-17 12:02
0.75.0-1+py315.1 arm64 build pass unknown not read yet 2026-08-17 12:03
0.75.0-1+py315.1 amd64 build pass unknown not read yet 2026-08-17 12:02
0.75.0-1+py315.1 all build pass unknown not read yet 2026-08-17 12:02