4.8.1-7 in the archive
tests failed,
ours is 4.8.1-7+py315.1.
Nothing recorded is waiting on this one.
published,
4.8.1-7+py315.1,
as work request 1040146,
which ended in work request 1040149.
Which turned out to be build-failed: the build failed: work request 1040149.
| 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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
4.8.1-7+py315.1
|
amd64 | test | fail | rebuilt | named none | — | 2026-09-02 21:25 |
4.8.1-7+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-02 19:38 |
4.8.1-7+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-19 07:03 |
4.8.1-7+py315.1
|
arm64 | test | fail | rebuilt | named none | — | 2026-08-19 07:20 |
4.8.1-7
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-18 21:20 |
4.8.1-7
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-18 21:20 |
4.8.1-7+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-19 07:20 |
4.8.1-7+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-19 07:15 |