1.0.5~ds-1 in the archive
build failed,
ours is 1.0.5~ds-1+py315.1.
left on 2026-10-01
Nothing recorded is waiting on this one.
aborted,
1.0.5~ds-1+py315.1,
as work request 1367883,
which ended in work request 1367885.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1367885.
| 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-5 |
the build log's installed set | not dated |
| 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-10-02 |
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 #1149296 (done) RM: git-remote-hg -- orphaned and superseeded |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.0.5~ds-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-28 17:18 |
1.0.5~ds-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-28 17:16 |