| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Hopefully this will fix intermittent test failures on AppVeyor.
|
| |
|
|
|
|
| |
Deleting random files tends to cause random test failures. The results are not
predictable and depend on the order in which files are uploaded and directories
created.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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.
|
| |
|
|
| |
Fixes test/backupstorefix.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Logging everything to stdout (so that Windows users can redirect it) causes
extra output on stdout that confused the Perl script for this test.
|
| |
|
|
|
|
|
| |
It seems that sending a NULL pointer to an ostringstream on FreeBSD gives
different results depending on the type of the pointer. It could write 0
or 0x0, and if they don't match, tests will fail.
|
| |
|
|
|
|
|
| |
Normally this will be done by housekeeping anyway, so it's not that useful,
but it's good to check for it in tests, especially when testing
BackupStoreCheck's ability to repair bad things that happened to the store
when they involve references.
|
| | |
|
| |
|
|
| |
Use them in testbackupstorefix to reduce code duplication.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Adds a nicer constructor and more helpful cleanup on QueryFinished()
to the auto-generated BackupProtocolLocal.
|
| | |
|
| |
|
|
|
|
|
| |
Fixes some cases where a directory might refer to an object that doesn't
exist, which is removed from the directory, but an object that depends on
it (a patch) isn't removed, and requires a subsequent recheck.
|
| | |
|
| |
|
|
|
|
|
| |
It's not safe to use an iterator after the underlying collection has
been modified. We need to restart iterating over the directory in that
case. Otherwise we could loop forever looking for an end() that we've
already passed, or start accessing unallocated memory.
|
| |
|
|
|
|
| |
Preparation work for better testing of fixing directories with entries
that no longer exist on disk. Related to debugging the problems reported
by Markus Grunwald.
|
| | |
|
| |
|
|
| |
removed properly.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Obsolete old (inconsistent) meaning of -q in bbackupquery.
Replace -q with -Wwarning or -Werror in tests to reduce noise and fix
tests.
Test that reading a nonexistent directory on the server doesn't crash
server or client.
Test that bbackupd does continue backup run and delete files when
storage limit is exceeded.
Use logging guards to hide expected warnings in testbbackupd.
Remove apparently pointless listing files on server at the end of
testbbackupd.
|
| |
|
|
|
| |
daemon can't clean up after itself.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
be seen as old enough to upload by bbackupd.
Fix comments.
|
| |
|
|
|
| |
is enough time.
|
| |
|
|
|
|
|
| |
Typo fix.
(refs #3)
|
| |
|
|
|
|
|
|
|
|
|
| |
Use #defined paths for executables to remove win32/unix differences.
Don't check for bbstored memory leaks on win32.
Wrap long lines for readability.
(refs #3)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All of these use lib/server/WinNamedPipeStream on Win32, so they don't
belong in lib/common.
Made LaunchServer() work on Win32.
Added constants for paths to executables, for use in tests, removing the
need for #ifdefs and clumsy DIRECTORY_SEPARATORs in paths.
Added terminate_bbackupd() and wait_for_operation() functions.
Update unit tests to #include "ServerControl.h" if they need it.
(refs #3)
|
| | |
|
| |
|
|
|
| |
Remove newlines from output to avoid failure to recognise it on Win32
|
| | |
|
| |
|
|
|
|
|
| |
- This is my current patch queue. I think that all of these are safe
to apply. This is just under half of the pending changes in
chris/general (the easy half).
|
| |
|
|
|
| |
This just renames all of the files that configure now substitutes - no changes to any of the files.
|
| |
|
|
|
| |
configure now detects perl executable location and updates all scripts to use the correct path; also adds PERL_EXECUTABLE define to BoxConfig.h. makebuildenv.pl adds PERL define to all makefiles.
|
| | |
|
| |
|
