aIbrahiim commented on PR #37702: URL: https://github.com/apache/beam/pull/37702#issuecomment-3954542809
@claudevdm The tests are being skipped, but its happening at collection time rather than execution time which cause pytest to fail The two failing tests are: sdks/python/apache_beam/ml/rag/enrichment/milvus_search_it_test.py -sdks/python/apache_beam/ml/rag/ingestion/milvus_search_it_test.py And heres my investigation: The ubuntu latest runner runs with -m require_docker_in_docker to execute only these two Milvus tests but both files import pymilvus at the module levels and when that import fails they raise unittest.SkipTest immediately before pytest can even collect the tests and since these are the only two files marked with require_docker_in_docker the pytest ends up collecting zero tests and returns exit code 5 "no tests collected" so the run_pytest.sh script treats this as a failure so i think if the tests were skipped during execution after being collected that would be fine but they are skipped during collection so pytest never sees any runnable tests -- 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]
