[Flaky Test] Multiple tests affected (Worker Process Issue)

[Muhammad-awawdi-amazon]

Test Name

Project-wide Jest tests

From the log, the tests are failing because the test harness tries to spin up a Redis cluster using cluster_manager.py start -r 4 -n 3 --cluster-mode, but it times out (“Timeout exceeded trying to wait for server 127.0.0.1:34011 to know all hosts”). Essentially, none of your actual test assertions are even getting exercised because the underlying cluster never finishes forming.

Here’s what’s going on:

The test spins up multiple Redis processes (3 shards, each with 4 replicas, so 12 total processes) via cluster_manager.py.

The script tries to verify that all Redis nodes see each other in a healthy cluster (checks the CLUSTER SLOTS output).

It times out, complaining that node 127.0.0.1:34011 never recognizes the rest of the cluster.

Since the cluster can’t be formed, your tests all fail at setup.

Once you see a line like:

`Exception: Timeout exceeded trying to wait for server 127.0.0.1:34011 to know all hosts

`…you know the root cause is that the local cluster never became “ready.” All subsequent errors (TypeError: Cannot read properties of undefined (reading 'getAddresses')) come from the fact that there’s no valid “cluster instance” created in the test.

Test Location

No response

Failure Permlink

https://github.com/valkey-io/valkey-glide/actions/runs/14015021895/job/39239662465#step:6:48765

Frequency

No response

Steps to Reproduce

No response

System Information

No response

Language and Version

No response

Engine Version

No response

Logs

Tests are completing successfully (492 failed, 8 skipped, 636 passed, out of 1136 total), but the test runner is reporting issues with worker process cleanup. The worker process is being force-exited instead of gracefully shutting down.

Screenshots

No response

Glide Version

No response

Expected Behavior

No response

Actual Behavior

No response

Possible Fixes

No response