Closed hbelmiro closed 3 days ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
@chensun we have several tests failing with Python 3.13. Can you please take a look? Also, I think we should have all tests using at least the minor and major supported Python versions (3.9 and 3.13).
cc @DharmitD @HumairAK
@chensun we have several tests failing with Python 3.13. Can you please take a look?
From SDK side, kfp-pipeline-spec is blocking Python 3.13 support. I sent a PR: https://github.com/kubeflow/pipelines/pull/11378, PTAL.
Also, I think we should have all tests using at least the minor and major supported Python versions (3.9 and 3.13).
No, I think it would be unnecessary and waste of resource to run all e2e or backend-integration tests with different Python versions. If we think SDK's main role as a YAML generator, as long as the produced YAML file doesn't change across Python versions--the SDK unit test guarantees that--they would work on the backend.
@chensun I reverted the changes to add 3.13 to all tests and left 3.13 only on those tests that use all Python versions. Can you please review?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: chensun
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Description of your changes: This PR adds support for Python 3.13 to tests. This is a follow-up for https://github.com/kubeflow/pipelines/pull/11372
Checklist: