| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
The protocol command didn't succeed, it just returned a result with an
unexpected type, so make the failure message reflect that and give details
of the response actually received, to help with debugging.
|
| | |
|
| |
|
|
|
| |
Allows the exception message to be captured before it goes out of scope.
|
| |
|
|
| |
Use them in testbackupstorefix to reduce code duplication.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
This is useful to return from a test if an assertion/check fails, instead of
throwing an exception.
Also add logging of the actual error code received (with name) to
TEST_COMMAND_RETURNS_ERROR(_OR).
|
| |
|
|
| |
Returns the number of errors found and fixed.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We pass a std::auto_ptr<SocketStream> to every Protocol subclass when we
construct it, and it takes control of this object. This reduces the risk of:
* accidentally reusing the same SocketStream for multiple Protocols
(it happened to me in testbackupstore);
* holding onto a reference to the SocketStream;
* allowing a locally-scoped SocketStream to go out of scope and be released
while still being referenced by a live Protocol.
|
| |
|
|
| |
Fix previous changes by waiting for forked bbstored process during termination.
|
| |
|
