Small fixes for non-fully-parallel sweep #12800
luke-gruberAnnotations
9 errors and 4 warnings
|
Windows 2025/Visual C++ 2022 (check)
The process 'C:\Program Files\Git\bin\bash.exe' failed with exit code 127
|
|
Windows 2025/Visual C++ 2022 (check)
Process completed with exit code 1.
|
|
Windows 2022/Visual C++ 2022 (check)
The process 'C:\Program Files\Git\bin\bash.exe' failed with exit code 127
|
|
Windows 2022/Visual C++ 2022 (check)
Process completed with exit code 1.
|
|
Windows 2025/Visual C++ 2022 (test-bundled-gems)
The process 'C:\Program Files\Git\bin\bash.exe' failed with exit code 127
|
|
Windows 2025/Visual C++ 2022 (test-bundled-gems)
Process completed with exit code 1.
|
|
Windows 11-arm/Visual C++ (btest test-basic test-tool)
The process 'C:\Program Files\Git\bin\bash.exe' failed with exit code 127
|
|
Windows 11-arm/Visual C++ (btest test-basic test-tool)
Process completed with exit code 1.
|
|
Windows result
Process completed with exit code 1.
|
|
Windows 2025/Visual C++ 2022 (check)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@90be1154f987f4dc0fe0dd0feedac9e473aa4ba8. 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/
|
|
Windows 2022/Visual C++ 2022 (check)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@90be1154f987f4dc0fe0dd0feedac9e473aa4ba8. 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/
|
|
Windows 2025/Visual C++ 2022 (test-bundled-gems)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@90be1154f987f4dc0fe0dd0feedac9e473aa4ba8. 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/
|
|
Windows 11-arm/Visual C++ (btest test-basic test-tool)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@90be1154f987f4dc0fe0dd0feedac9e473aa4ba8. 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/
|