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

← All states

Where it stands

built, ours is 8.1.7+dfsg-1+py315.2.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev

Nothing recorded is waiting on this one.

What was sent

published, 8.1.7+dfsg-1+py315.2, as work request 1245741.

Sent before this one: 7.1.1-2+py315.1, 8.1.7+dfsg-1+py315.1. A version that was sent is spent, whatever came of it.

What is known

QuestionAnswerSaid byAs of
Why did the build fail? unknown
The log was read and says nothing this tool recognises. These are the failures somebody has to look at.
deps/11 not dated
was the interpreter under test installed? no
its chroot had a different Python installed instead, so its failure is about whatever that one is: these take their interpreter from the default rather than from pybuild
python3.14_3.14.7-1
the build log's installed set not dated
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

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
8.1.7+dfsg-1+py315.2 arm64 build pass unknown not read yet — 2026-09-09 10:10
8.1.7+dfsg-1+py315.2 amd64 build pass unknown not read yet — 2026-09-09 10:25
8.1.7+dfsg-1+py315.2 all build pass unknown not read yet — 2026-09-09 10:24
8.1.7+dfsg-1+py315.1 arm64 build pass unknown not read yet — 2026-09-09 09:17
7.1.1-2+py315.1 arm64 build fail unknown not read yet — 2026-08-18 01:53