The bug was opened to track a potential bugs on armel(or others slow
archs, but it does not always happened).
Fix from upstream[0] may take a long time so if you use the package please keep in mind about this unless the bug was closed.
Thanks your detailed analysis for it. I have uploaded -3 to unstable to
hope to unblock tox migrating. But these are some unexpected maybe.
This will lead a autopkgtest on s390x[0] again from its tracker page[1] to get the link(UTC+8 13:06 2024/03/22).
But another retry on s390x it passed on s390x[2].
[0]: https://ci.debian.net/packages/t/tox-current-env/testing/s390x/44235641/ [1]: https://tracker.debian.org/pkg/tox-current-env
[2]: https://ci.debian.net/packages/t/tox-current-env/
Do you think I will need to upload it to unstable again with `sorted`
for `test_allenvs_print_deps_to_file` as I analyzed above?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 12:05:33 |
Calls: | 6,706 |
Files: | 12,236 |
Messages: | 5,350,979 |