Open omnivagant opened 1 month ago
I'm assuming you are using Botan 2.x, right? During the development of TLS 1.3 in Botan 3.x we raised this timeout (and improved the steering of this test case), because we saw a similar flaky behavior in our CI.
@randombit Should we backport this, perhaps?
In AlpineLinux we noticed that parts of this test would sometimes timeout on some architectures, most often
loongarch64
andriscv64
:Raising this timeout helps: