workflows: Capture Docker in Docker tests in beam_PreCommit_Python_Coverage workflow

[mohamedawnallah]

Motivation and Context

Addresses #35920 (comment)

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[mohamedawnallah]

Hey @damccorm, I think this PR would solve this issue #35920 (comment). It turned out that ML tests run also in that workflow beam_PreCommit_Python_Coverage so we need to add the filtering for tests that require_docker_in_docker i.e Milvus tests

[damccorm]

Thanks - trying this here - https://github.com/apache/beam/actions/runs/17220391007

[github-actions]

Assigning reviewers:

R: @Abacn for label build.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[mohamedawnallah]

Thanks - trying this here - https://github.com/apache/beam/actions/runs/17220391007

The tests beam_PreCommit_Python_Coverage running on ubuntu-latest variant exits with code value 5 which indicates no tests to run. This due to the fact (as yet) Milvus dependencies not added properly (existing follow-up PR #35920) so the tests with pytest marker require_docker_in_docker are skipped

SKIPPED [1] apache_beam/ml/rag/enrichment/milvus_search_it_test.py:72: unittest.case.SkipTest: Milvus dependencies not installed: No module named 'pymilvus'

[mohamedawnallah]

Removing now the ubuntu-latest from beam_PreCommit_Python_Coverage since we're gonna add it later in this PR #35816

[damccorm]

Instead of including python_version, could we include the os? That way the generated job names will be different per job

[mohamedawnallah]

Instead of including python_version, could we include the os? That way the generated job names will be different per job

Added OS label to workflow (job_name and test results). Perhaps we can leave the python_version since this workflow currently runs on the default python version which is 3.9 in future potentially this can run on multiple python versions?

[mohamedawnallah]

Hey @damccorm, can you please take another look? I have removed Pposargs from this PR as per this comment #35954 (comment)

[mohamedawnallah]

Cherry-picking those commits in that PR #35920. Closing this PR