[RFR] AIPMDM-888: Simplify OSS Metaflow core tests to be more Pythonic / pytest-friendly / tox-friendly #37
Tingting-ChangAnnotations
22 errors and 14 warnings
|
core-azure
The run was canceled by @Tingting-Chang.
|
|
core-azure
No test report files were found
|
|
core-azure
The operation was canceled.
|
|
core-gcs
The run was canceled by @Tingting-Chang.
|
|
core-local
The run was canceled by @Tingting-Chang.
|
|
core-gcs
No test report files were found
|
|
core-local
No test report files were found
|
|
core-gcs
The operation was canceled.
|
|
core-local
The operation was canceled.
|
|
core-argo
The run was canceled by @Tingting-Chang.
|
|
core-argo
No test report files were found
|
|
core-argo
The operation was canceled.
|
|
core-batch
The run was canceled by @Tingting-Chang.
|
|
core-batch
No test report files were found
|
|
core-batch
The operation was canceled.
|
|
core-k8s
The run was canceled by @Tingting-Chang.
|
|
core-k8s
No test report files were found
|
|
core-k8s
The operation was canceled.
|
|
Core Integration Tests
The run was canceled by @Tingting-Chang.
|
|
core-sfn
The run was canceled by @Tingting-Chang.
|
|
core-sfn
No test report files were found
|
|
core-sfn
The operation was canceled.
|
|
core-azure
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-azure
No file matches path junit-core-azure.xml
|
|
core-gcs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-local
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-gcs
No file matches path junit-core-gcs.xml
|
|
core-local
No file matches path junit-core-local.xml
|
|
core-argo
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/upload-artifact@v4, azure/setup-helm@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-argo
No file matches path junit-core-argo.xml
|
|
core-batch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/upload-artifact@v4, azure/setup-helm@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-batch
No file matches path junit-core-batch.xml
|
|
core-k8s
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/upload-artifact@v4, azure/setup-helm@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-k8s
No file matches path junit-core-k8s.xml
|
|
core-sfn
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/upload-artifact@v4, azure/setup-helm@v4, dorny/test-reporter@d61b558e8df85cb60d09ca3e5b09653b4477cea7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
core-sfn
No file matches path junit-core-sfn.xml
|