1.4.5-1 in the archive
build failed,
ours is 1.4.5-1+py315.2.
Nothing recorded is waiting on this one.
aborted,
1.4.5-1+py315.2,
as work request 1346713,
which ended in work request 1346715.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1346715.
Sent before this one:
1.4.5-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? |
tests-failed
the test suite failed, cause not narrowed. The tests failed under the new interpreter and nothing here recognises why. =================================== FAILURES =================================== |
deps/11 | 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 #1149345 pyprof2calltree: FTBFS against python 3.15rc2 (module 'cProfile' has no attribute 'label') |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.4.5-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 02:27 |
1.4.5-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-26 03:33 |
1.4.5-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-26 04:48 |