6.1.3-1 in the archive
build failed,
ours is 6.1.3-1+py315.2.
Nothing recorded is waiting on this one.
aborted,
6.1.3-1+py315.2,
as work request 1346770,
which ended in work request 1346772.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1346772.
Sent before this one:
6.0.3-1+py315.1, 6.1.3-1+py315.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As 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-time-machine 3.5.0-3+py315.1: we publish 3.5.1-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 |
| 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 #1149341 python-aioswitcher: FTBFS against python 3.15rc2 (exception message wording changed) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
6.1.3-1
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-09-24 21:06 |
6.1.3-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 02:36 |
6.1.3-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-19 17:14 |
6.0.3-1
|
amd64 | test | fail | archive | 3.13, 3.14, 3.15 | — | 2026-08-22 09:15 |
6.0.3-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-22 12:40 |