| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
Previously, files were uploaded using bbackupd, which did it in the order that
it read the directories, which was OS-dependent. So destroying certain fixed
RaidFiles would have an unpredictable effect on the store. Now, we write a manifest
when creating the test files, and upload them in exactly that order, so that the
ID of each file will always be the same.
|
| |
|
|
|
|
|
|
| |
pure C++.
Allows it to work with Visual Studio and no Cygwin/MSYS shell.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Avoid using the rm command, and use the correct name for the test executables
compiled by our cmake alternate build system.
|
|
|
|
|
| |
Perl on Windows tends to use IPv6 for localhost if possible, but the server binds
to IPv4, breaking the test.
|
|
|
|
|
| |
StopServer() does a hard terminate on Windows, which can leave temporary files
in place, causing problems later in the test.
|
|
|
|
|
| |
Con is a special filename on Windows and you just can't create a file with
that name.
|
|
|
|
|
| |
Otherwise when the counts differ later, we won't know whether we did the setup
properly in the first place or not.
|
|
|
|
|
| |
I think something is on the PATH in Appveyor that makes rmdir /s/q fail,
especially when run through Perl.
|
|
|
|
| |
Break dependendency of test/bbackupd on individual files from other modules.
|
|
|
|
| |
Fixes test/backupstorefix.
|
|
|
|
| |
wrong
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
Merge branch 'master' of https://github.com/agrandville/boxbackup into appveyor
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This test has always been fragile, and usually fails on Travis for reasons
unknown, so replace the log parsing and intercepts with simple mocking code.
This doesn't cover 100% of what the old test did, including diff timer aborts
and the number of blocks used by the uploaded files, but it should be
completely robust.
|
| | |
| | |
| | |
| | |
| | | |
"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.
|
| |
|