Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
We now work on the assumption that a single "job", pulled from
the queue, might contain multiple "test" objects. These are
the instances of the protocol-testers which we actually execute.
This is part of #9558.
|
|
Rather than passing our settings-object around, as well as
specific settings that are read from it, just pass the object.
The worker can read the settings directly if/when it needs to.
|
|
This replaces redis as a hard-wired default.
|
|
This means we can queue/dequeue to either Redis or Beanstalkd.
|
|
last one.
|
|
|
|
|
|
|
|
We can now sleep between retesting, and we configure the
number of repeats via the configuration file.
|
|
|
|
|
|
implement a "duration" method.
|
|
|
|
file shortly.
|
|
|
|
|
|
anything else running under beanstalkd.
|
|
match what we did with the alerts.
|
|
|
|
|
|
|
|
zero.
|
|
|
|
to invoke it from that. Currently alerts are disabled. TODO: Fix
this.
|
|
|
|
generate tests.
|
|
|
|
|