Ensure commands are processed before shutting down persistence threads

Prevents race condition where test cleanup closes persistence threads while
there are still enqueued operations. Normally the content layer shall ensure
that all enqueued operations are aborted before reaching this step, but this
does not take place in the simplified testing setup.

1 files changed, 1 insertions, 1 deletions

diff --git a/storage/src/tests/persistence/filestorage/sanitycheckeddeletetest.cpp b/storage/src/tests/persistence/filestorage/sanitycheckeddeletetest.cpp
index b906c9f67d6..961d2628052 100644
--- a/storage/src/tests/persistence/filestorage/sanitycheckeddeletetest.cpp
+++ b/storage/src/tests/persistence/filestorage/sanitycheckeddeletetest.cpp
@@ -65,7 +65,7 @@ void SanityCheckedDeleteTest::delete_bucket_fails_when_provider_out_of_sync() {
     // Send a put to another bucket to serialize the operation (guaranteed
     // since we only have 1 thread and the delete always has max priority).
     c.sendPut(syncBucket, DocumentIndex(0), PutTimestamp(1001));
-    c.top.waitForMessages(1, MSG_WAIT_TIME);
+    c.top.waitForMessages(2, MSG_WAIT_TIME);
     // Should still be able to get identical bucket info for bucket.
     spi::BucketInfoResult infoResult(
             _node->getPersistenceProvider().getBucketInfo(spiBucket));