Use p310_ml_test

Author: aIbrahiim

.github/trigger_files/beam_PostCommit_Yaml_Xlang_Direct.json

@@ -1,4 +1,4 @@
 {
   "comment": "Modify this file in a trivial way to cause this test suite to run",
-  "revision": 4
+  "revision": 5
 }

.github/workflows/beam_PostCommit_Yaml_Xlang_Direct.yml

@@ -80,7 +80,7 @@ jobs:
       - name: run PostCommit Yaml Xlang Direct script
         uses: ./.github/actions/gradle-command-self-hosted-action
         with:
-          gradle-command: :sdks:python:postCommitYamlIntegrationTests -PyamlTestSet=${{ matrix.test_set }} -PbeamPythonExtra=ml_test,yaml
+          gradle-command: :sdks:python:postCommitYamlIntegrationTests -PyamlTestSet=${{ matrix.test_set }} -PbeamPythonExtra=p310_ml_test,yaml
       - name: Archive Python Test Results
         uses: actions/upload-artifact@v7
         if: failure()

sdks/python/setup.py

@@ -601,10 +601,11 @@ def get_portability_package_data():
               # tests due to tag check introduced since pip 24.2
               # https://github.com/apache/beam/issues/31285
               # 'xgboost<2.0',  # https://github.com/apache/beam/issues/31252
-              # tft needs protobuf>=3.20.3,<5 and google-cloud-dataflow-client
-              # (gcp extra) needs protobuf>=4.25.8, so protobuf must be in
-              # [4.25.8, 5). tf2onnx 1.16.x caps protobuf<4 and is therefore
-              # unresolvable here; 1.17+ drops that cap (protobuf>=3.20).
+              # ml_test + gcp is unresolvable on Python 3.10: tft pulls in
+              # tensorflow-metadata 1.14.x (protobuf<4.21) while
+              # google-cloud-dataflow-client needs protobuf>=4.25.8. Yaml
+              # Xlang CI uses p310_ml_test instead (no tft). tf2onnx 1.17+
+              # avoids an additional protobuf<4 cap from tf2onnx 1.16.x.
               'tf2onnx>=1.17.0,<1.18',
           ] + ml_base_core,
           'p310_ml_test': [