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

built, ours is 1.7.3-3+py315.1, waiting on python-gevent.

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

What was sent

published, 1.7.3-3+py315.1, as work request 1217281.

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

What is known

QuestionAnswerSaid byAs of
Why did the build fail? superseded-dependency
Built against our own rebuild of a dependency, one generation back. The run is evidence, unlike an archive copy: re-run it against the current suite before reading the failure.
python3-zope.interface 8.5-3+py315.1: we publish 8.6-1+py315.1
deps/11 not dated
Which known interpreter change does this failure show? tests-failed
the test suite failed, cause not narrowed. The tests failed under the new interpreter and nothing here recognises why.
=================================== FAILURES ===================================
deps/11 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
does the release team track this? dependency level 6
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong.
amd64 bad, arm64 bad, armhf bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad
release.debian.org, from their ben tracker 2026-09-16 04:49 UTC
has anybody reported this under the usertag? 1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks
#1146356 (done) python-yappi: FTBFS against python 3.15rc1
the BTS usertag not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
1.7.3-3+py315.1 arm64 test pass rebuilt named none 2026-09-02 16:00
1.7.3-3+py315.1 amd64 test pass rebuilt named none 2026-09-02 16:00
1.7.3-3+py315.1 arm64 build pass unknown not read yet 2026-09-02 15:59
1.7.3-3+py315.1 amd64 build pass unknown not read yet 2026-09-02 15:59
1.7.3-2 arm64 test fail the archive's (reference arm) 3.13, 3.15 2026-08-20 03:11
1.7.3-2 amd64 test fail the archive's (reference arm) 3.13, 3.15 2026-08-20 03:11
1.7.3-2+py315.1 amd64 build fail unknown not read yet 2026-08-20 08:47