3.14.7-3 in the archive
built,
ours is 3.14.7-4+py315.2.
ahead of the archive (built from a source sid does not have)
Rebuilding it releases 96 packages waiting on it, as this stage last counted.
published,
3.14.7-2+py315.2,
as work request 1127935,
which ended in work request 1127945.
Which turned out to be tests-aborted: the tests were stopped: work request 1127945.
Sent before this one:
3.14.7-1+py315.1.
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.7-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 |
|---|---|---|---|---|---|---|---|
3.14.7-4+py315.2
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-27 11:25 |
3.14.7-4+py315.2
|
amd64 | build | pass | unknown | not read yet | — | 2026-08-27 16:30 |
3.14.7-4+py315.2
|
all | build | pass | unknown | not read yet | — | 2026-08-27 16:24 |
3.14.7-1+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-26 19:47 |
3.14.7-1+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-26 19:47 |
3.14.7-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-26 19:47 |