Skip to content

Commit

Permalink
[testing] Bump client recv timeout to 10 sec
Browse files Browse the repository at this point in the history
The 2 sec timeout is typically enough, but some unit tests
do call stuff which could end up having to wait for disk
(compact db for instance) and on the CV builders we run
a lot of the test concurrently which may slow things down
a lot so we've seen a number of unit tests fails due
too aggressive timeouts.

Change-Id: I3618629c7f26e58432f0073e6190035742cd8062
Reviewed-on: https://review.couchbase.org/c/kv_engine/+/180586
Tested-by: Build Bot <build@couchbase.com>
Reviewed-by: Dave Rigby <daver@couchbase.com>
  • Loading branch information
trondn authored and daverigby committed Sep 29, 2022
1 parent 5659f36 commit 725554d
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions protocol/connection/client_connection.cc
Expand Up @@ -280,8 +280,9 @@ MemcachedConnection::MemcachedConnection(std::string host,
// cluster
timeout = std::chrono::minutes{30};
} else {
// When running in unit tests we want it to fail fast
timeout = std::chrono::seconds{2};
// When running in unit tests we want it to fail fast, but not
// too fast as the CV builders are sometimes heavily loaded
timeout = std::chrono::seconds{10};
}

if (ssl) {
Expand Down

0 comments on commit 725554d

Please sign in to comment.