0.3.7 in the archive
build failed,
ours is 0.3.7+py315.3.
Nothing recorded is waiting on this one.
aborted,
0.3.7+py315.3,
as work request 1407285,
which ended in work request 1407287.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1407287.
Sent before this one:
0.3.7+py315.1, 0.3.7+py315.2.
A version that was sent is spent, whatever came of it.
| 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 |
| was the interpreter under test installed? |
no
its chroot had a different Python installed instead, so its failure is about whatever that one is: these take their interpreter from the default rather than from pybuild python3.14_3.14.8-1 |
the build log's installed set | 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.7+py315.3
|
all | build | fail | unknown | not read yet | — | 2026-10-02 08:06 |
0.3.7+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-24 23:16 |
0.3.7+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-25 21:09 |