gc: Fix hang during repack in partial clones #624
lucamilanesioAnnotations
22 errors and 7 warnings
|
test (macos-latest, 3.6)
The version '3.6' with architecture 'arm64' was not found for macOS 15.7.4.
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
|
|
test (macos-latest, 3.7)
The version '3.7' with architecture 'arm64' was not found for macOS 15.7.4.
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
|
|
test (macos-latest, 3.12)
Process completed with exit code 1.
|
|
test (macos-latest, 3.11)
Process completed with exit code 1.
|
|
test (macos-latest, 3.10)
Process completed with exit code 1.
|
|
test (macos-latest, 3.9)
Process completed with exit code 1.
|
|
test (macos-latest, 3.8)
Process completed with exit code 1.
|
|
test (macos-latest, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1
[notice] To update, run: python3.8 -m pip install --upgrade pip
|
|
test (windows-latest, 3.12)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (windows-latest, 3.8)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (windows-latest, 3.9)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (windows-latest, 3.11)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (windows-latest, 3.7)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (windows-latest, 3.6)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (windows-latest, 3.10)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (ubuntu-20.04, 3.9)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (ubuntu-20.04, 3.10)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (ubuntu-20.04, 3.6)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (ubuntu-20.04, 3.8)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (ubuntu-20.04, 3.11)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (ubuntu-20.04, 3.7)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (ubuntu-20.04, 3.12)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (macos-latest, 3.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|
|
test (macos-latest, 3.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|
|
test (macos-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|
|
test (macos-latest, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|
|
test (macos-latest, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|
|
test (macos-latest, 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|
|
test (macos-latest, 3.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
|