aIbrahiim commented on PR #39007: URL: https://github.com/apache/beam/pull/39007#issuecomment-4740154139
> Are these milvus tests still running in any of the test suites? Can you confirm? yes, I checked and they're still running. There are currently two active Milvus integration test files: - ingestion/milvus_search_it_test.py - enrichment/milvus_search_it_test.py Both are marked with @pytest.mark.require_docker_in_docker, and they are included in the PreCommit Python ML workflow and they run on the ubuntu latest runner with Python 3.13 and the failing job is the one that runs apache_beam/ml/ -m require_docker_in_docker, so the Milvus tests are definitely still part of the test suite and that's where the container startup timeout is happening `WARNING apache_beam.ml.rag.test_utils:test_utils.py:201 Retry 2/3: Failed to start Milvus DB container. Reason: Port mapping for container 166f055b71eda80e14ff7076a4c3d714e6af6ba1f718227eac3fe91c8c564b94 and port 43681 is not available.` `WARNING apache_beam.ml.rag.utils:utils.py:210 Milvus client connection after container start attempt 1 failed: <MilvusException: (code=2, message=Fail connecting to server on localhost:36461, illegal connection params or server unavailable)>. Retrying in 2.00 seconds... WARNING apache_beam.ml.rag.utils:utils.py:210 Milvus client connection after container start attempt 2 failed: ... Retrying in 2.40 seconds... ... [attempts 3-21] ... WARNING apache_beam.ml.rag.utils:utils.py:210 Milvus client connection after container start attempt 21 failed: ... Retrying in 76.68 seconds.` `___ ERROR at setup of TestMilvusVectorWriterConfig.test_write_with_batching ____` @claudevdm -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
