From 0868ed92c7b234a14a99414e7d1340cdf9841b80 Mon Sep 17 00:00:00 2001 From: Albert Chu Date: Tue, 27 Aug 2024 18:41:34 +0000 Subject: [PATCH] t: cover FLUX_KVS_SYNC without backing store Problem: There is no coverage to ensure FLUX_KVS_SYNC does not work if there is no backing store. Add coverage in t1010-kvs-commit-sync.t. --- t/t1010-kvs-commit-sync.t | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/t/t1010-kvs-commit-sync.t b/t/t1010-kvs-commit-sync.t index db3ba60d82a9..e7e743c363a8 100755 --- a/t/t1010-kvs-commit-sync.t +++ b/t/t1010-kvs-commit-sync.t @@ -18,13 +18,17 @@ checkpoint_get() { jq -j -c -n "{key:\"$1\"}" | $RPC content.checkpoint-get } -test_expect_success 'load content module' ' - flux module load content +test_expect_success 'load content module and kvs' ' + flux module load content && + flux module load kvs +' + +test_expect_success 'sync does not work without a backing store' ' + test_must_fail flux kvs put --sync testsync=1 ' test_expect_success 'load content-sqlite and kvs and add some data' ' flux module load content-sqlite && - flux module load kvs && flux kvs put a=1 && flux kvs put b=2 '