Tests: Add mesh shader API tests for Metal backend #4406
MikhailGorobetsbuild-windows.yml
on: push
Win10 -> Pre-checks
22s
Matrix: build
Annotations
27 errors and 10 warnings
|
Win10 -> Win10-x64, Release
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> Win10-x64, Release
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> Win10-x64, Release
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> UWP-x64, Release
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> UWP-x64, Release
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> UWP-x64, Release
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> Win10-Ninja-x64, Debug
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> Win10-Ninja-x64, Debug
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> Win10-Ninja-x64, Debug
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> Win10-x64, Debug
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> Win10-x64, Debug
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> Win10-x64, Debug
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> MinGW-x64, Release
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> MinGW-x64, Release
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> MinGW-x64, Release
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> Win10-Win32, Release
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> Win10-Win32, Release
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> Win10-Win32, Release
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> Win10-Win32, Debug
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> Win10-Win32, Debug
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> Win10-Win32, Debug
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> Win10-Dev-x64, RelWithDebInfo
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> Win10-Dev-x64, RelWithDebInfo
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> Win10-Dev-x64, RelWithDebInfo
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> UWP-x64, Debug
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
|
|
Win10 -> UWP-x64, Debug
Fetched in submodule path 'ThirdParty/SPIRV-Cross', but it did not contain b28b4e4c28c309bb8042bb196bd1170e2c07baa8. Direct fetching of that commit failed.
|
|
Win10 -> UWP-x64, Debug
remote error: upload-pack: not our ref b28b4e4c28c309bb8042bb196bd1170e2c07baa8
|
|
Win10 -> Pre-checks
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/
|
|
Win10 -> Win10-x64, Release
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/
|
|
Win10 -> UWP-x64, Release
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/
|
|
Win10 -> Win10-Ninja-x64, Debug
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/
|
|
Win10 -> Win10-x64, Debug
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/
|
|
Win10 -> MinGW-x64, Release
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/
|
|
Win10 -> Win10-Win32, Release
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/
|
|
Win10 -> Win10-Win32, Debug
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/
|
|
Win10 -> Win10-Dev-x64, RelWithDebInfo
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/
|
|
Win10 -> UWP-x64, Debug
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/
|