You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In AlpineLinux we noticed that parts of this test would sometimes timeout on some architectures, most often loongarch64 and riscv64:
tls_stream_integration:
Server ran 44 tests 3 FAILED
Failure 1: Server: timeout in accept
Failure 2: Server: timeout in accept
Failure 3: Server: timeout in accept
Raising this timeout helps:
--- a/src/tests/test_tls_stream_integration.cpp+++ b/src/tests/test_tls_stream_integration.cpp@@ -33,7 +33,7 @@ using ssl_stream = Botan::TLS::Stream<ne
using namespace std::placeholders;
using Result = Botan_Tests::Test::Result;
-static const auto k_timeout = std::chrono::seconds(3);+static const auto k_timeout = std::chrono::seconds(6);
static const auto k_endpoints = std::vector<tcp::endpoint> {tcp::endpoint{net::ip::make_address("127.0.0.1"), 8082}};
enum { max_msg_length = 512 };
The text was updated successfully, but these errors were encountered:
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.
In AlpineLinux we noticed that parts of this test would sometimes timeout on some architectures, most often
loongarch64
andriscv64
:Raising this timeout helps:
The text was updated successfully, but these errors were encountered: