ERROR api/tests/test_containers_integration_tests/libs/broadcast_channel/redis/test_sharded_channel.py::TestShardedRedisBroadcastChannelClusterIntegration::test_cluster_sharded_pubsub_delivers_message - redis.exceptions.ResponseError: CONFIG SET failed (possibly related to argument 'cluster-announce-ip') - Cluster announce IP must be a valid IPv4 or IPv6 address2026-05-06 01:06:48,813.813 INFO [MainThread] [conftest.py:74] - DifyTestContainers initialized - ready to manage test containers ====== 2389 passed, 8 skipped, 907 warnings, 1 error in 208.26s (0:03:28) ====== no error ERROR api/tests/test_containers_integration_tests/libs/broadcast_channel/redis/test_sharded_channel.py::TestShardedRedisBroadcastChannelClusterIntegration::test_cluster_sharded_pubsub_delivers_message - redis.exceptions.ResponseError: CONFIG SET failed (possibly related to argument 'cluster-announce-ip') - Cluster announce IP must be a valid IPv4 or IPv6 address2026-05-06 01:06:48,813.813 INFO [MainThread] [conftest.py:74] - DifyTestContainers initialized - ready to manage test containers ====== 2389 passed, 8 skipped, 907 warnings, 1 error in 208.26s (0:03:28) ======

TL;DR

The issue is likely due to a missing configuration file and an invalid Redis cluster announce IP, which can be fixed by ensuring the existence of the vdb.env file and setting a valid IP address for the cluster-announce-ip configuration.

Guidance

• Verify that the vdb.env file exists at the specified path /home/runner/work/dify/dify/api/tests/integration_tests/ and contains the required configuration settings.
• Check the Redis configuration to ensure that the cluster-announce-ip is set to a valid IPv4 or IPv6 address.
• Review the test setup to ensure that the vdb.env file is being properly created or copied to the correct location before running the tests.
• Consider updating the test to handle the case where the vdb.env file does not exist or the cluster-announce-ip is not set.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to the test environment setup and configuration. Ensuring the existence of the vdb.env file and setting a valid cluster-announce-ip should resolve the issue. However, without more information about the test setup and configuration, it is difficult to provide a more detailed solution.

Recommendation

Apply workaround: Ensure the vdb.env file exists and contains the required configuration settings, and set a valid IP address for the cluster-announce-ip configuration. This should resolve the issue and allow the tests to run successfully.