Looks like it's the same thing as the Debian bug 857753.
Created attachment 735811 [details] websockets-9.1-r1-build.log
I haven't been able to reproduce this, even when emulating m68k. Could you please retry with WEBSOCKETS_TESTS_TIMEOUT_FACTOR=100 set? If that doesn't work, try 1000.
WEBSOCKETS_TESTS_TIMEOUT_FACTOR=100 helps, then the tests fail with AssertionError: Items in the first set but not the second: 'The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.' Which (the fact that the time-out factor helps, not the assertion errors) match the Debian assessment of the problem.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=df822423436f87dcd357ff2e2af57e041135d661 commit df822423436f87dcd357ff2e2af57e041135d661 Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2021-10-30 07:52:06 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2021-10-30 07:52:06 +0000 dev-python/websockets: Fix tests on slower systems for 9.1 Infuriatingly, this approach makes one of the 10.0 tests fail consistently on my fast desktop. Bug: https://bugs.gentoo.org/810094 Signed-off-by: James Le Cuirot <chewi@gentoo.org> dev-python/websockets/websockets-9.1-r1.ebuild | 3 +++ 1 file changed, 3 insertions(+)
Closing bugs for old versions with the new stabilization round. If you can still reproduce with the newest ~arch version, feel free to reopen.