2.16.0.2-2 in the archive
built,
ours is 2.16.0.2-2+py315.1.
Nothing recorded is waiting on this one.
published,
2.16.0.2-2+py315.1,
as work request 1432131.
Sent before this one:
2.15.0.1-1+py315.1, 2.15.0.1-1+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.7-4 |
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 |
| 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 #1143437 (done) waagent: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.14 --parallel=2 returned exit code 13 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.16.0.2-2+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-10-08 04:41 |
2.15.0.1-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 05:58 |
2.15.0.1-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-20 13:13 |