Currently not all specs from the suite are run, as some are tagged with redis.
These require a real Redis server, no reason not to run them against CI as well.
While getting CI to run the rest of the suite I realized the plugin isn't always interruptible.
In case of data_type => channel and data_type => pattern_channel the Redis API used is blocking (simply waits forever until more data comes in) thus the change to use an alternative "timeout" APIs with these.
Currently not all specs from the suite are run, as some are tagged with
redis. These require a real Redis server, no reason not to run them against CI as well.While getting CI to run the rest of the suite I realized the plugin isn't always interruptible. In case of
data_type => channelanddata_type => pattern_channelthe Redis API used is blocking (simply waits forever until more data comes in) thus the change to use an alternative "timeout" APIs with these.