[EXT2FS] Fix an uninitialized variable usage RTC failure #455
SigmaTel71build.yml
on: push
MSBuild (i386)
23m 50s
Matrix: build-clang-cl
Matrix: build-linux
Matrix: build-msvc-arm
Matrix: build-msvc
Annotations
33 warnings
|
build-msvc-arm (windows-latest, 14.29, arm64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-latest, 14.29, arm64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-latest, 14, arm64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-latest, 14, arm64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-2022, 14, arm, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-2022, 14, arm, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-2022, 14.29, arm, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc-arm (windows-2022, 14.29, arm, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14, amd64, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14.2, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14, i386, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14.2, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14.2, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14.2, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-clang-cl (amd64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-msvc (windows-latest, 14, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-clang-cl (i386, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-clang-cl (amd64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
build-clang-cl (i386, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
MSBuild (i386)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
|
|
build-linux (gcc, amd64, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (clang, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (gcc, i386, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (gcc, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (clang, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (clang, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (clang, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (gcc, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (gcc, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
|
build-linux (gcc, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
reactos-clang-amd64-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
459 MB |
sha256:6dd64ac52063635db8cdd07138fa40395f19c8ff47016335687c720ffdacb1e1
|
|
|
reactos-clang-amd64-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
173 MB |
sha256:a08cbcd014aab3679acfb2e5ce0eee0e34dc5adfe89b77104a6372088bbd0268
|
|
|
reactos-clang-cl-amd64-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
143 MB |
sha256:74f6ed516903ee03ba706683f962c064b12105d589b0fda2742eaf5ff8550ba2
|
|
|
reactos-clang-cl-amd64-Release-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
133 MB |
sha256:fcff1a3ee96b1a7166d92eb3c4413444c3bf3bfd27c2e1d27c36f9fda76f6175
|
|
|
reactos-clang-cl-i386-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
145 MB |
sha256:b21ec768fbc341312bb6b5dd633b1177d83c56ab7a19131246d37ed30c549ad9
|
|
|
reactos-clang-cl-i386-Release-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
132 MB |
sha256:89e73d924989017d7a0eb3fd72a9c590a8cae69a36dd9237a8930764c01fabfc
|
|
|
reactos-clang-i386-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
215 MB |
sha256:a7f1edddc9f1de4f0fda9d99f1843234b83ace2c41fac7e52d37660790d908db
|
|
|
reactos-clang-i386-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
172 MB |
sha256:bcd7c23fcafc694d34d0204202fade0c008cc78335abaca36571bb7d4fa7f82e
|
|
|
reactos-gcc-amd64-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
427 MB |
sha256:e4d9fdb93b6b566f624156fc1152e6b59e59c7a75eee1500946c3da014ebdf65
|
|
|
reactos-gcc-amd64-Debug-0x600-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
427 MB |
sha256:43055120af4aa80e04bcfc68c5e5e3921a50cd085ee3e2940204b0cc3909d060
|
|
|
reactos-gcc-amd64-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
177 MB |
sha256:b01a01980ead2525f6107269c61dd0ff3e879181b017460e6462cfced6413264
|
|
|
reactos-gcc-i386-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
206 MB |
sha256:8530579c8b7a16f30cc9fd575120691e20ca1150a67bc57e1e7746bfb1863dec
|
|
|
reactos-gcc-i386-Debug-0x600-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
207 MB |
sha256:9f16f24a84c849d26b047b0607fdde7c766f23ea1a950bbcfcc94d458dd2015b
|
|
|
reactos-gcc-i386-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
192 MB |
sha256:cb6766c7a1373f6b8cdba55a4c012a036849c9846e36e6873fa6427353664c90
|
|
|
reactos-msvc14-amd64-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
150 MB |
sha256:f153df598430383988faf2e30758053fc31d272a43bfea47befc4c9df68e1db8
|
|
|
reactos-msvc14-amd64-Debug-0x600-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
150 MB |
sha256:72407b07e14e718da0bfd6203c44999a145b666ef2c8dcacc6aa84b9af60eafe
|
|
|
reactos-msvc14-amd64-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
138 MB |
sha256:0b3ec6b526685518c640af3b2d8f99db2a34e89ce3fe1fad1a9656b18e1128d1
|
|
|
reactos-msvc14-arm-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
12.7 MB |
sha256:98a292af95cfa896d90180ca6257f74bceed33fef090036566fbe90484385a96
|
|
|
reactos-msvc14-arm-Release-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
10.8 MB |
sha256:449d9176ce844f8a4be95e42aa3a5d58f99ff2925d492b629e5d3d20c1d1fede
|
|
|
reactos-msvc14-arm64-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
3.2 MB |
sha256:0984e11dc7cdb985026ebb8fa088dc32d4f8ce04ddfc5c6c2c1eacd343e2f2d2
|
|
|
reactos-msvc14-arm64-Release-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
3.09 MB |
sha256:f56a10ffe43642b2ce432a9f3ed511c0b48bb40bb93f579ebf88c6800fda5bdb
|
|
|
reactos-msvc14-i386-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
154 MB |
sha256:24fa960980468bf275c731a081f2098f2f5d7850d7e0e886a6b96c433e19e8f6
|
|
|
reactos-msvc14-i386-Debug-0x600-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
154 MB |
sha256:6cbb8cc5342936b175f4213007b97a1ba5769802cd9300b20fef10135800f4e1
|
|
|
reactos-msvc14-i386-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
131 MB |
sha256:655fdbfb26ec75e6df9daada0c8cc86982e3616549189c5c3a1c810394e1f982
|
|
|
reactos-msvc14.2-amd64-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
150 MB |
sha256:41cbb1240a107211a963c6c1f31475b5c0f0df1b0830b6caf7be6144ca24ee54
|
|
|
reactos-msvc14.2-amd64-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
138 MB |
sha256:6ed8a744254bea7159a38675a4449bc24695bb2f5a5c6fbf1f91cc6c9ed12fd8
|
|
|
reactos-msvc14.2-i386-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
154 MB |
sha256:9be882479dcc6bb71ff8ad70309f724058ac7b162c84db3a6e94de141bae1c1d
|
|
|
reactos-msvc14.2-i386-Release-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
130 MB |
sha256:42f44472535e58c85a9a01101abcef307eccf7fea552533486f9c6d801de790a
|
|
|
reactos-msvc14.29-arm-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
12.7 MB |
sha256:1b01a4fec677b9037dc414c7e73c325f33afb7b7a7c88cd77b6f524797bfd0f4
|
|
|
reactos-msvc14.29-arm-Release-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
10.7 MB |
sha256:af75e9b63c943ea0eb474864380770d4a5d9ea3d87283db3786f93702953c97f
|
|
|
reactos-msvc14.29-arm64-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
3.2 MB |
sha256:fb3a98f9e314f4b845ad326e3b474512b44b88b66d3d28d49b5562167b7378c3
|
|
|
reactos-msvc14.29-arm64-Release-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
3.07 MB |
sha256:ee27925f157e5f7792e6c74c8ef0567ffd9f0d9b8d153cff3ab06793b493d8a4
|
|
|
reactos-syms-clang-cl-amd64-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
103 MB |
sha256:537f9a6c507d7d723e24cfc5ce8341b0851d9a35bed2504fc60725f4f487cf93
|
|
|
reactos-syms-clang-cl-i386-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
112 MB |
sha256:892aef93c3709359c1dcfdbb40c8b5f9711ea3c6b6df05159f04351e40d8f83b
|
|
|
reactos-syms-msvc14-amd64-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
226 MB |
sha256:5d33f73fbd4e0c6d1703086e8636281275e6855f1d58d3dba3aabcf4be42a574
|
|
|
reactos-syms-msvc14-amd64-Debug-0x600-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
226 MB |
sha256:efc57c55b8f8389cf22f69088ded982a479f8882bb2890fa7dc56959d6ba2eda
|
|
|
reactos-syms-msvc14-arm-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
54.7 MB |
sha256:0f1b278d00a922e111bfd620185efa74f02d3f7e5eef2af9a0744d9255813c97
|
|
|
reactos-syms-msvc14-arm64-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
7.73 MB |
sha256:de960041613013dec1c5692029a027fb79517e8183c8c0b9e7492a83dbe635a1
|
|
|
reactos-syms-msvc14-i386-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
233 MB |
sha256:5abdd3becf0c4120751d7873de50015fa95f5024b5c84ac93826107f3c40e567
|
|
|
reactos-syms-msvc14-i386-Debug-0x600-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
233 MB |
sha256:8e6a2276ba59b5025f2e41f7be5b0c67c587f08dc32c3af95ae20f3a1f4b4dd6
|
|
|
reactos-syms-msvc14.2-amd64-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
211 MB |
sha256:004332ba1f4966199f8abde5878cf8a214e5b9cd6121478a0507aed67f07efa6
|
|
|
reactos-syms-msvc14.2-i386-Debug-0x502-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
217 MB |
sha256:59fc629868f41b5ba011072a870d02b8c18d365e7e9f11f91b89801359c783c3
|
|
|
reactos-syms-msvc14.29-arm-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
50.4 MB |
sha256:20310a4042206d3fad971ea0f1bda7d32ea5f028d3c179946bad9e299b06ab72
|
|
|
reactos-syms-msvc14.29-arm64-Debug-d436f2e76b13d3dc24df8953135c620adbd0cb70
|
7.31 MB |
sha256:c02fa8022d3fc8965d2bb166b7e81cfac766d9e75a6ba25d2f28e30071a7a741
|
|