0.3.11-1 in the archive, ships a compiled extension
build failed,
ours is 0.3.11-1+py315.d.1.
python3-all-without-dev
add python3-all-dev; python3-all brings interpreters, not headers
Nothing recorded is waiting on this one.
aborted,
0.3.11-1+py315.d.1,
as work request 1275654,
which ended in work request 1275656.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1275656.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
unknown
The log was read and says nothing this tool recognises. These are the failures somebody has to look at. |
deps/11 | not dated |
| 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.3.11-1
|
arm64 | test | pass | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-15 03:29 |
0.3.11-1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-15 06:32 |
0.3.11-1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-15 06:34 |