3.24.22+ds-2 in the archive
build failed,
ours is 3.24.22+ds-2+py315.1.
Nothing recorded is waiting on this one.
aborted,
3.24.22+ds-2+py315.1,
as work request 1460953,
which ended in work request 1460955.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1460955.
Sent before this one:
3.24.22+ds-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 |
| Which known interpreter change does this failure show? |
module-not-importable
a dependency was not importable. Nothing here says the interpreter caused this. An import that failed usually means the testbed was assembled before the dependency had been rebuilt, which is ours to fix by running it again. E ModuleNotFoundError: No module named 'onnxruntime.capi.onnxruntime_pybind11_state'. Although a module with this name was found for a different Python version (onnxruntime_pybind11_state.cpython-314-x86_64-linux-gnu.so). could not import onnxruntime.capi.onnxruntime_pybind11_state |
deps/11 | 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.24.22+ds-2
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-10-14 09:15 |
3.24.22+ds-2+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-10-14 09:38 |
3.24.22+ds-1
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-10-13 09:23 |
3.24.22+ds-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-10-13 09:25 |