| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | |
| | | |
"context" might easily be used in a test function, and doesn't follow our
naming convention anyway, so renamed to sTlsContext.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
See discussion of incompatible struct packing on ARM processors:
http://lists.boxbackup.org/pipermail/boxbackup/2010-November/005818.html
http://lists.boxbackup.org/pipermail/boxbackup/2011-February/005978.html
Thanks to Leif Linderstam for identifying the problem and proposing a
solution. This is just a test for the problem, not a fix in itself.
|
|/ |
|
|
|
|
| |
Switch httpserver daemon start/stop to use standard functions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a new exception code to represent an object being completely missing (not
found on the store at all), separate from not being found in a particular
directory.
Improve mapping of server-side exceptions to protocol error messages returned
to the client.
Add handling for missing exceptions, such as
BackupStoreException::PatchChainInfoBadInDirectory, and the new
BackupStoreException::ObjectDoesNotExist.
Fix mapping for BackupStoreException::CouldNotFindEntryInDirectory to make it
distinguistable from BackupStoreException::ObjectDoesNotExist.
|
| |
|
|
|
|
|
| |
Stop the client while waiting for housekeeping, to ensure that it doesn't
prevent housekeeping from running and cause the test to fail.
|
| |
|
|
|
|
|
| |
Also checks the returned error code, and gives more useful diagnostics on
failure.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Once again, the Windows issue of being unable to delete or overwrite an
open file causes issues. In this case it's only test failures. We need to
be diligent about closing open file handles and protocol sessions in tests.
|
|
|
|
|
|
|
|
|
|
|
| |
The old assertion, that the write lock file exists before starting checking,
was erroneously passing before when no lock was held, because the lockfile
was never deleted. Now that we delete it when unlocking the account, this
started causing test failures.
Changed the way that accounts are checked for errors to use a function that
acquires a write lock first, and modified test to disconnect open clients
before starting checking the account, to fix it.
|
|
|
|
|
| |
I needed reliable exit codes to run the tests in a loop to catch an
intermittent failure.
|
|
|
|
|
| |
NamedLock simply didn't work before. This may cause test failures, but the
tests are already failing on Windows, and must be fixed.
|
| |
|
|
|
|
| |
Files need to be closed before renaming over them on Windows.
|
| |
|
|
|
|
|
|
| |
It was checking for raidfiles files that have different filenames in release
and debug builds, and that aren't even deleted by the test in release builds.
|
| |
|
|
|
|
|
| |
Should make the Travis logs shorter and more readable.
|
|
|
|
|
|
| |
Logging everything to stdout (so that Windows users can redirect it) causes
extra output on stdout that confused the Perl script for this test.
|
| |
|
|
|
|
|
| |
They cause a lot of noise in the Travis build logs.
|
|
|
|
| |
for reporting.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|