0.7.33 in the archive
build failed,
ours is 0.7.33+py315.2.
Nothing recorded is waiting on this one.
aborted,
0.7.33+py315.2,
as work request 1347198,
which ended in work request 1347200.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1347200.
Sent before this one:
0.7.32+py315.1, 0.7.33+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 |
| 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 #1149307 reprotest: FTBFS against python 3.15rc2 (pip install coverage diffoscope pytest fails with "No package metadata was found") |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.7.33
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-24 21:06 |
0.7.33+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 03:26 |
0.7.33+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-21 19:39 |
0.7.32+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-06 14:00 |
0.7.32
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-06 09:38 |
0.7.32+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-06 13:56 |