1.3.1-2 in the archive
not needed yet,
ours is 1.3.1-3+py315.2,
waiting on python-async-timeout, python-hiredis, python-pytest-cov.
ahead of the archive (built from a source sid does not have)
Nothing recorded is waiting on this one.
published,
1.3.1-3+py315.2,
as work request 1120969,
which ended in work request 1120979.
Which turned out to be tests-aborted: the tests were stopped: work request 1120979.
Sent before this one:
1.3.1-2+py315.1, 1.3.1-2+py315.2, 1.3.1-2+py315.3.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does the archive build this version? |
archive ftbfs
Debian's own rebuild of the version the archive carries fails too, so this failure is not the new interpreter's doing. It still blocks the transition: nobody can rebuild it until that is fixed. amd64 arm64 |
tests.reproducible-builds.org | 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 |
| 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 #1058292 aioredis: FTBFS: FAILED tests/multi_exec_test.py::test_global_loop |
the BTS usertag | not dated |
No run in this phase yet — it is not needed yet.