0.8.0~a3-1 in the archive
build failed,
ours is 0.8.0~a3-1+py315.3.
Nothing recorded is waiting on this one.
aborted,
0.8.0~a3-1+py315.3,
as work request 1345374,
which ended in work request 1345392.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1345392.
Sent before this one:
0.8.0~a3-1+py315.1, 0.8.0~a3-1+py315.2.
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-numcodecs 0.17.0+ds-1.1~+py315.2: we publish 0.17.0+ds-2+py315.1 python3-psutil 7.1.0-1.1+py315.2: we publish 7.2.2-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 #1149526 napari: FTBFS against python 3.15rc2 (test_selection_collision fails with pixel_10 == [0, 0, 0, 255]) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.8.0~a3-1+py315.3
|
all | build | fail | unknown | not read yet | — | 2026-09-24 22:15 |
0.8.0~a3-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-06 21:28 |
0.8.0~a3-1
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-01 15:27 |
0.8.0~a3-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-01 19:26 |