| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
Stop the client while waiting for housekeeping, to ensure that it doesn't
prevent housekeeping from running and cause the test to fail.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It's not safe to assume that we can get into the store before housekeeping runs,
so don't try. Just wait for housekeeping to run and check that all the files are
deleted afterwards.
|
| |
|
|
|
|
|
| |
Refactor all common code from testbbackupd and testbackupstore to allow other
test suites to contain multiple tests and execute selected tests more easily.
Report all test results within a suite in a standard, easy to read summary.
|
| | |
|
| | |
|
| |
|
|
|
| |
I needed reliable exit codes to run the tests in a loop to catch an
intermittent failure.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This stops stale daemons from hanging around if a single test fails because
it throws an exception, which otherwise would cause the whole suite to
abort immediately without cleaning up after itself.
|
| |
|
|
|
| |
This just results in huge console noise if we can't kill a daemon for some
reason. Kill them once, after all tests have run, instead.
|
| |
|
|
|
| |
BSD tar seems to not like additional options after the first block.
|
| |
|
|
|
|
| |
Test now passes reliably with any verbosity level on NetBSD, despite
the really slow compares.
|
| |
|
|
|
|
| |
Running a compare takes far too long on NetBSD (3 seconds) and this was
messing up the timing of the test.
|
| |
|
|
|
|
|
|
| |
fail.
We didn't take into account the time taken to perform a compare as part of
the test, when deciding how long to wait for bbackupd to recover.
|
| |
|
|
| |
Hopefully will help anyone trying to debug this test in future.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The shorter delay on error, introduced recently to speed up test runs,
combined with a guess about how long bbackupd would take to run a backup
and discover that the client store marker had changed, meant that sometimes
the daemon would have discovered the problem, aborted, waited and run again
while the test was waiting for the first failure.
Synchronising with the running daemon using bbackupctl wait_for_sync_end
should make the test timing accurate enough. We also tighten the recovery
timing checks to make sure that it's doing what it should.
|
| |
|
|
|
| |
We're using an internal daemon here, so we don't want an external one as well.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Older versions of GNU tar fail to set the timestamps on symlinks, which makes
them appear too recent/new to be backed up immediately, causing
test_bbackupd_uploads_files() for example to fail. Fixed by restoring the
timestamps manually after extracting the fixture archive.
For more details about the issue in tar, please see:
http://lists.gnu.org/archive/html/bug-tar/2009-08/msg00007.html
http://git.savannah.gnu.org/cgit/tar.git/plain/NEWS?id=release_1_24
This resulted in symlinks in fixture test files
|
| |
|
|
|
|
|
|
| |
This makes the tests run ~300 seconds faster, and coincidentally somehow
fixes or prevents a test failure on FreeBSD on this test, probably some
race condition.
|
| |
|
|
| |
Use them in testbackupstorefix to reduce code duplication.
|
| |
|
|
|
| |
Fix a couple of compiler warnings, and don't continue the test if we failed
to load the configuration file.
|
| |
|
|
|
|
| |
Thanks to Jean-Yves Moulin for reporting this issue. When bbackupd is configured
to create locations whose names contain a slash, it was impossible to escape it,
and thus to enter the directory in bbackupquery to inspect or restore it.
|
| |
|
|
|
|
|
| |
This caused the issue reported by Brendon Baumgartner and described in my
email to the Box Backup list on Mon, 21 Apr 2014 at 18:44:38. If the directory
disappears then we used to try to send an empty attributes block to the server,
which is illegal.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Split single monolithic test into many smaller ones, which can be run
separately. Allows easier testing of new features in isolation.
Merged back changes from the test refactor branch to reduce diffs.
|
| |
|
|
|
| |
Reduces warnings about network operations with no timeout. May prevent some
hangs that might have occurred waiting forever for network data in the past.
|
| |
|
|
| |
Merged back changes from the test refactor branch to reduce diffs.
|
| |
|
|
|
|
| |
Makes way for more use of local protocol objects and protocol subclasses.
Merged back changes from the test refactor branch to reduce diffs.
|
| |
|
|
| |
Merged back changes from the test refactor branch to reduce diffs.
|
| |
|
|
|
|
| |
Hopefully all of these changes are inconsequential.
Merged back changes from the test refactor branch to reduce diffs.
|
| |
|
|
|
|
|
|
|
| |
Merged back changes from the test refactor branch to reduce diffs.
Fix wrong setting of log level in compare() function.
We want to only show errors if we expect mismatches, and show warnings if we
didn't expect mismatches. I had it the other way around before.
|
| |
|
|
|
|
|
| |
For some reason the timing changed and the test was no longer waiting for the
same length of time as bbackupd, causing it to fail.
Merged back changes from the test refactor branch to reduce diffs.
|
| | |
|
| |
|
|
|
|
|
|
| |
Similar to TEST_COMMAND_RETURNS_ERROR_OR, but allows any command or sequence
to cause the error, without direct access to the command message.
Refactor so that TEST_COMMAND_RETURNS_ERROR_OR calls TEST_PROTOCOL_ERROR_OR
to make the assertion on the last error seen by the protocol.
|
| |
|
|
| |
We don't really need these, so clean up by removing them.
|
| |
|
|
|
|
|
|
| |
Conflicts:
bin/bbackupd/BackupDaemon.cpp
bin/bbackupd/BackupDaemon.h
test/bbackupd/testbbackupd.cpp
|
| | |
|
| |
|
|
|
| |
It's incompatible with having a logger that logs everything, regardless of
the global log level.
|
