Pull the redis interceptor spec out of quarantine
What does this MR do and why?
ERR timeout is not an integer or out of range
which was the original reason to quarantine the spec.
It is not exactly clear from #373026 (closed) how flaky it was.
I tried to replay it many times on my machine, and run multiple pipelines on this MR - it was not replicated
Instead, I was hitting Redis command PIPELINE/MULTI arguments hash to different slots
both on CI and locally which is resolved by prefixing the keys with the {}
part as described in https://docs.gitlab.com/ee/development/redis.html#multi-key-commands
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #373026 (closed)