Skip to content

test: Fix failing SDK test by replacing mock.patch with subprocess for actual build #292

test: Fix failing SDK test by replacing mock.patch with subprocess for actual build

test: Fix failing SDK test by replacing mock.patch with subprocess for actual build #292

Triggered via pull request October 14, 2024 21:45
Status Success
Total duration 26s
Artifacts

kfp-sdk-runtime-tests.yml

on: pull_request
Matrix: kfp-runtime-tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
kfp-runtime-tests (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
kfp-runtime-tests (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
kfp-runtime-tests (3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
kfp-runtime-tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/