Skip to content

Commit 0d3c183

Browse files
committed
Fix intermittent QSPagingTest failures due to periodic pager runs
The pager is set to run every 5s by default, which messes up the test expectations on some of the tests. Change-Id: Ie9b4f01b8ef0ae7271fa11836d2d2e233b516bdc Reviewed-on: https://review.couchbase.org/c/kv_engine/+/189986 Reviewed-by: James H <[email protected]> Tested-by: Build Bot <[email protected]>
1 parent 02e162c commit 0d3c183

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

tests/testapp_cluster/quota_sharing_paging_test.cc

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,11 @@ class QSPagingTest : public ClusterTest {
3939
}
4040

4141
static void SetUpTestCase() {
42-
cluster = Cluster::create(1);
42+
cluster = Cluster::create(1, {}, [](auto&&, auto& config) {
43+
// Don't run the item pager at a set interval, as this interferes
44+
// with some of the tests which depend on ep_num_pager_runs.
45+
config["quota_sharing_pager_sleep_time_ms"] = 300'000;
46+
});
4347
}
4448

4549
static void TearDownTestCase() {
@@ -216,6 +220,9 @@ class QSPagingTest : public ClusterTest {
216220
{"replicas", 0},
217221
{"max_vbuckets", maxVBuckets},
218222
{"cross_bucket_ht_quota_sharing", true},
223+
// Don't run the item pager at a set rate, as that affects the
224+
// tests which depend on the ep_num_pager_runs stat.
225+
{"pager_sleep_time_ms", 300'000},
219226
// Setting the increment factor to 0 means we always increment
220227
{"freq_counter_increment_factor", 0},
221228
// Keep checkpoint memory usage minimal

0 commit comments

Comments
 (0)