Age | Commit message (Collapse) | Author |
|
As soon as we allow multiple test-implementations we get
into a mess, as Mauve regards an ID as unique and that is
based upon the test-definition not the implementing method
We want to allow:
* HTTPS test to succeed.
* SSL-check to fail.
Which means multiple tests of type "https" will have different
IDs. Force this by adding on the class of the implementation.
|
|
|
|
|
|
The redis-state "alerter" saves state in a useful way for the
future, and will now save an array of hashes - each has corresponding
to a useful result.
|
|
|
|
We now record:
custodian.$type.$host.test_duration [time]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Credit to reddit user knothead for spotting this bug.
Fixes #4386.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This will mean historically we can see what the failure reason was.
|
|
* Added debian recommendation for mauvealert-client
|
|
|
|
|
|
|
|
not used.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|