[CICD] Merge multiple chip pipelines into a single one #13
Darryl233all_tests.yml
on: pull_request
Ascend tests
/
checkout_and_config
4s
MetaX tests
/
checkout_and_config
5s
check_docker_changes
3s
Matrix: Ascend tests / unit_tests
Matrix: MetaX tests / unit_tests
Matrix: Ascend tests / functional_tests_benchmark / functional_test_benchmark
Waiting for pending jobs
Matrix: Ascend tests / functional_tests_hetero_train / functional_test_hetero_train
Waiting for pending jobs
Matrix: Ascend tests / functional_tests_inference / functional_test_inference
Waiting for pending jobs
Matrix: Ascend tests / functional_tests_serve / functional_test_serve
Waiting for pending jobs
Matrix: Ascend tests / functional_tests_train / functional_test_train
Waiting for pending jobs
Matrix: MetaX tests / functional_tests_benchmark / functional_test_benchmark
Waiting for pending jobs
Matrix: MetaX tests / functional_tests_hetero_train / functional_test_hetero_train
Waiting for pending jobs
Matrix: MetaX tests / functional_tests_inference / functional_test_inference
Waiting for pending jobs
Matrix: MetaX tests / functional_tests_serve / functional_test_serve
Waiting for pending jobs
Matrix: MetaX tests / functional_tests_train / functional_test_train
Waiting for pending jobs
Matrix: CUDA tests / unit_tests
Waiting for pending jobs
Matrix: CUDA tests / functional_tests_benchmark / functional_test_benchmark
Waiting for pending jobs
Matrix: CUDA tests / functional_tests_hetero_train / functional_test_hetero_train
Waiting for pending jobs
Matrix: CUDA tests / functional_tests_inference / functional_test_inference
Waiting for pending jobs
Matrix: CUDA tests / functional_tests_serve / functional_test_serve
Waiting for pending jobs
Matrix: CUDA tests / functional_tests_train / functional_test_train
Waiting for pending jobs
Verify all platform tests
Annotations
8 errors and 7 warnings
|
Ascend tests / unit_tests (ascend910) / unit-ascend910
Process completed with exit code 1.
|
|
Ascend tests / all_tests_complete
Process completed with exit code 1.
|
|
MetaX tests / unit_tests (c500) / unit-c500
Process completed with exit code 1.
|
|
MetaX tests / all_tests_complete
Process completed with exit code 1.
|
|
CUDA tests / cli_validation / functional_test_cli
The run was canceled forcefully by @Darryl233.
|
|
all_tests
The run was canceled forcefully by @Darryl233.
|
|
all_tests
The run was canceled forcefully by @Darryl233.
|
|
all_tests
The run was canceled forcefully by @Darryl233.
|
|
Ascend tests / checkout_and_config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
MetaX tests / checkout_and_config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
CUDA tests / checkout_and_config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
MetaX tests / cli_validation / functional_test_cli
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Ascend tests / cli_validation / functional_test_cli
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Ascend tests / unit_tests (ascend910) / unit-ascend910
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
MetaX tests / unit_tests (c500) / unit-c500
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|