Skip to content

Upgrade WASDK from 1.6 to 1.8 #777

Upgrade WASDK from 1.6 to 1.8

Upgrade WASDK from 1.6 to 1.8 #777

Re-run triggered April 1, 2026 19:06
Status Failure
Total duration 9m 52s
Artifacts 6

build.yml

on: pull_request
Matrix: new-experiment
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 18 warnings
new-experiment (3, wasm)
Process completed with exit code 1.
new-experiment (2, wasm)
Process completed with exit code 1.
new-experiment (3, wasdk)
Process completed with exit code 1.
project-template
Process completed with exit code 1.
new-experiment (2, uwp)
Process completed with exit code 1.
wasm-linux
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/setup-dotnet@v4, actions/upload-artifact@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/
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExpStyle_xBind.CiTestExpStyle_xBind()'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp.ArrangeOverride(Size)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp.MeasureOverride(Size)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp_xBind.Element_PointerEntered(object, PointerRoutedEventArgs)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp_xBind.OnMyPropertyChanged(string, string)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp_ClassicBinding.Element_PointerEntered(object, PointerRoutedEventArgs)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp_ClassicBinding.OnMyPropertyChanged(string, string)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExpStyle_xBind.CiTestExpStyle_xBind()'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp.ArrangeOverride(Size)'
wasm-linux
Missing XML comment for publicly visible type or member 'CiTestExp.MeasureOverride(Size)'
Xaml-Style-Check
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/setup-dotnet@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-tooling
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/setup-dotnet@v4, actions/upload-artifact@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/
new-experiment (3, wasm)
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/setup-dotnet@v4, actions/upload-artifact@v4, al-cheb/configure-pagefile-action@v1.4, microsoft/setup-msbuild@v2. 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/
new-experiment (2, wasm)
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/setup-dotnet@v4, actions/upload-artifact@v4, al-cheb/configure-pagefile-action@v1.4, microsoft/setup-msbuild@v2. 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/
new-experiment (3, wasdk)
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/setup-dotnet@v4, actions/upload-artifact@v4, al-cheb/configure-pagefile-action@v1.4, microsoft/setup-msbuild@v2. 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/
project-template
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/setup-dotnet@v4, al-cheb/configure-pagefile-action@v1.4, microsoft/setup-msbuild@v2. 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/
new-experiment (2, uwp)
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/setup-dotnet@v4, actions/upload-artifact@v4, al-cheb/configure-pagefile-action@v1.4, microsoft/setup-msbuild@v2. 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/

Artifacts

Produced during runtime
Name Size Digest
linux-logs
990 KB
sha256:3a44307575133ebb48cf35b5ac300ef2ff6b2b2a65150ff757e9fee8607d8ade
new-experiment-logs-uwp-winui2
1.73 MB
sha256:741197b4c7a67827407e29b79af96d8ff7123eec9a49245f2625ec0ac9bfc805
new-experiment-logs-wasdk-winui3
1.42 MB
sha256:6a3194c98cef5896eb53aa5657a21065c32b47a4f287de869de4ab33f8e307ab
new-experiment-logs-wasm-winui2
1.38 MB
sha256:883dc1e63563be4f3c9ff50251e07d05dd200d90b847bd4898f5c4e45ce2ba2a
new-experiment-logs-wasm-winui3
1.38 MB
sha256:9e9bcfcce17e2c70596d81f1d86f75d1a7a5cd6d6f917c0e40b57b421db24e2f
test-tooling-logs
752 KB
sha256:8e3c8572d5c70cd0b22c68758380f7cddec6fe1b54284e1c81d48f47077094b8