6.7.0-1 in the archive
build failed,
ours is 6.7.0-1+py315.1,
waiting on httpx, poetry-core, pydantic, pyjwt, python-aiohttp, python-aioresponses, python-poetry-dynamic-versioning, python-pytest-asyncio, python-pytest-cov, requests.
Nothing recorded is waiting on this one.
aborted,
6.7.0-1+py315.1,
as work request 1408387,
which ended in work request 1408389.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1408389.
Sent before this one:
6.1.0-1+py315.1, 6.1.0-1+py315.2, 6.1.0-1+py315.3.
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 #1149611 (done) auth0-python: FTBFS against python 3.15rc2 ('Python/3.15.0rc2' != 'Python/3.15.0') |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
6.7.0-1
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-10-02 15:27 |
6.7.0-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-10-02 16:54 |
6.1.0-1+py315.3
|
all | build | fail | unknown | not read yet | — | 2026-09-24 22:19 |
6.1.0-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-08-27 22:56 |
6.1.0-1
|
amd64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-27 03:28 |