0.0.6 in the archive
build failed,
ours is 0.0.6+py315.1.
Nothing recorded is waiting on this one.
aborted,
0.0.6+py315.1,
as work request 1288575,
which ended in work request 1288577.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1288577.
Sent before this one:
0.0.1+py315.1, 0.0.3+py315.1, 0.0.5+py315.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| 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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.0.6+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-16 15:45 |
0.0.5
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-15 21:18 |
0.0.5+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-15 21:27 |
0.0.3
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-15 15:46 |
0.0.3+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-15 16:36 |
0.0.1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-03 19:03 |
0.0.1
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-03 15:29 |
0.0.1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-03 19:01 |