0.5.1.54.g802fa86-2 in the archive, ships a compiled extension
build failed,
ours is 0.5.1.54.g802fa86-2+py315.d.1.
left on 2026-09-18
Nothing recorded is waiting on this one.
aborted,
0.5.1.54.g802fa86-2+py315.d.1,
as work request 1286875,
which ended in work request 1286877.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1286877.
| Question | Answer | Said by | As of |
|---|---|---|---|
| do Debian's own tests pass? |
archive tests fail
Debian's own tests for this package fail in unstable, so this failure is not the new interpreter's doing. debci answers about the source rather than about the version we rebuilt, which is why the date its run happened is shown. amd64, arm64, last run 2026-09-05 |
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 #1147451 (done) RM: pyemd -- unmaintained and unused |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.5.1.54.g802fa86-2
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
0.5.1.54.g802fa86-2
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
0.5.1.54.g802fa86-2+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-16 13:11 |
0.5.1.54.g802fa86-2+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-16 13:11 |