0.6 in the archive
built,
ours is 0.6+py315.1.
Nothing recorded is waiting on this one.
published,
0.6+py315.1,
as work request 1305143.
Sent before this one:
0.3+py315.1, 0.4+py315.1, 0.5+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-ast-serialize 0.8.0+0gitfc05930-2+py315.1: we publish 0.9.0-1+py315.1 python3-mypy 2.2.0-4+py315.2: we publish 2.3.1-3+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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.6+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-18 17:07 |
0.6
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-18 15:10 |
0.6+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-18 17:05 |
0.5+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-14 03:17 |
0.4+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-10 16:13 |
0.4
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-10 15:28 |
0.4+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-10 16:06 |
0.3+py315.1
|
amd64 | test | pass | rebuilt | named none | ok | 2026-08-17 16:23 |
0.3
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-08-17 16:22 |
0.3+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-17 16:21 |