Skip to content

Release

Release #2981

Triggered via schedule March 23, 2026 18:16
Status Failure
Total duration 2m 48s
Artifacts

release.yml

on: schedule
Generate build matrix
1m 17s
Generate build matrix
Matrix: Staging Release
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 9 warnings
Staging Release (cu122)
The process '/usr/bin/git' failed with exit code 128
Staging Release (cu122)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu122)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu122)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu122)
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Staging Release (cu121)
The process '/usr/bin/git' failed with exit code 128
Staging Release (cu121)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu121)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu121)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu121)
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Staging Release (cpu)
The process '/usr/bin/git' failed with exit code 128
Staging Release (cpu)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cpu)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cpu)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cpu)
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Staging Release (cu118)
The process '/usr/bin/git' failed with exit code 128
Staging Release (cu118)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu118)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu118)
unable to access 'https://github.com/Oneflow-Inc/oneflow/': Failed to connect to 192.168.1.30 port 7890: Connection refused
Staging Release (cu118)
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Generate build matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, Oneflow-Inc/get-oneflow/cache-complete/matrix/build@ci-test-with-cu118. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Staging Release (cu122)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Staging Release (cu122)
Unable to clean or reset the repository. The repository will be recreated instead.
Staging Release (cu121)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Staging Release (cu121)
Unable to clean or reset the repository. The repository will be recreated instead.
Staging Release (cpu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Staging Release (cpu)
Unable to clean or reset the repository. The repository will be recreated instead.
Staging Release (cu118)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Staging Release (cu118)
Unable to clean or reset the repository. The repository will be recreated instead.