fix(test): fix a timing issue in pubsub test #3498
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Recent github action have encountered sporadic errors, such as case https://github.com/redis/go-redis/actions/runs/17021636203/job/48251478581?pr=3481 (This also occurred in PR #3496 , but I couldn't find the error logs after resubmitting).
The error log:
Reason
The reason is that after sending the ssubscribe command, the pubsub shardchannels command was immediately called without waiting for Redis to process the ssubscribe command, resulting in unexpected results.
Solution
sleep 10ms to wait for Redis to finish processing the command.