You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have an option to retrigger testing on one particular host.
Example:
I have 2 hosts: 1st and 2nd.
on 1st host testing was stopped on date A.
on 2nd host testing was stopped on date B.
I need to restore testing from dates when it was stopped.
Basically I need to retrigger:
from date A for 1st host
from date B for 2nd host
To be able use such scenario some extra key , like "--retrigger_host" is required. It should identify host, where you need to retrigger testing. It can be identified via name ip or other way (depends on how code is communicating with hosts).
E.g.:
$ redis-benchmarks-spec-cli --use-branch --from-date 2023-02-03 --retrigger_host [name1 or ip1 or ...] --redis_port *** --redis_host *** --redis_pass ***
$ redis-benchmarks-spec-cli --use-branch --from-date 2023-02-10 --retrigger_host [name2 or ip2 or ...] --redis_port *** --redis_host *** --redis_pass ***
Implementation of such functionality will add flexibility to system and help in restoring of testing system from failures w/o extra load for other testing hosts.
The text was updated successfully, but these errors were encountered:
Totally agree, let's add a new argument to the cli (that needs to be included on the buidler STREAM metadata ) to filter based upon platform name.
So, potentially something like: --platform
Improvement
I'd like to have an option to retrigger testing on one particular host.
Example:
Basically I need to retrigger:
To be able use such scenario some extra key , like "--retrigger_host" is required. It should identify host, where you need to retrigger testing. It can be identified via name ip or other way (depends on how code is communicating with hosts).
E.g.:
Implementation of such functionality will add flexibility to system and help in restoring of testing system from failures w/o extra load for other testing hosts.
The text was updated successfully, but these errors were encountered: