From a3136e31a7b3cca64918b142e10e57d1f956ee2b Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Thu, 9 Apr 2009 22:44:58 +0000 Subject: Show reasons for waiting during bbackupd and backupstorepatch tests, to help with interpreting test output. When running at Trace level, where extra output from bbackupd etc. is common, log a single line at the start of waiting, instead of progress dots, to help with interpreting output. Show number of seconds waited for on Windows as well as Unixes. --- test/backupstorepatch/testbackupstorepatch.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/backupstorepatch/testbackupstorepatch.cpp') diff --git a/test/backupstorepatch/testbackupstorepatch.cpp b/test/backupstorepatch/testbackupstorepatch.cpp index 4fbf296a..23b01b15 100644 --- a/test/backupstorepatch/testbackupstorepatch.cpp +++ b/test/backupstorepatch/testbackupstorepatch.cpp @@ -578,7 +578,7 @@ int test(int argc, const char *argv[]) #ifdef WIN32 // Cannot signal bbstored to do housekeeping now, // so just wait until we're sure it's done - wait_for_operation(12); + wait_for_operation(12, "housekeeping to run"); #else // Send the server a restart signal, so it does // housekeeping immediately, and wait for it to happen -- cgit v1.2.1