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

build failed, ours is 5.6-10+py315.1.

Nothing recorded is waiting on this one.

What was sent

aborted, 5.6-10+py315.1, as work request 1088873, which ended in work request 1088875.

Which turned out to be build-failed: the workflow ended: build-failed, work request 1088875.

What is known

QuestionAnswerSaid byAs of
Why did the build fail? archive-dependency
Built against the archive's copy of a dependency we have rebuilt. The ordering has not reached it, so this is not the package's own fault.
python3-brotli 1.2.0-4: we publish 1.2.0-4+py315.1
python3-zopfli 0.4.3-1+py315.1: we publish 0.4.3-2+py315.1
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 the archive build this version? archive ftbfs
Debian's own rebuild of the version the archive carries fails too, so this failure is not the new interpreter's doing. It still blocks the transition: nobody can rebuild it until that is fixed.
amd64
arm64
tests.reproducible-builds.org 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
5.6-10 arm64 test fail the archive's (reference arm) named none 2026-08-22 15:25
5.6-10 amd64 test fail the archive's (reference arm) named none 2026-08-22 15:25
5.6-10+py315.1 arm64 build fail unknown not read yet 2026-08-22 21:10
5.6-10+py315.1 amd64 build fail unknown not read yet 2026-08-22 21:09
5.6-10+py315.1 all build fail unknown not read yet 2026-08-22 21:08