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

← Failures

Where it stands

build failed, ours is 1.20.0-8+py315.2.

Nothing recorded is waiting on this one.

What was sent

timeout, 1.20.0-8+py315.2, as work request 1347761.

Sent before this one: 1.20.0-8+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-psutil 7.1.0-1.1+py315.2: we publish 7.2.2-1+py315.1
deps/11 not dated
does Debian's own test suite pass? neutral
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
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
#1149255 tahoe-lafs: FTBFS against python 3.15rc2
the BTS usertag not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
1.20.0-8+py315.2 all build fail unknown not read yet — 2026-09-25 10:40
1.20.0-8+py315.1 all build fail unknown not read yet — 2026-09-17 19:03