Skip to content

[SEH][GCC] Prevent inlining of functions using REACTOS seh pragma #105

[SEH][GCC] Prevent inlining of functions using REACTOS seh pragma

[SEH][GCC] Prevent inlining of functions using REACTOS seh pragma #105

Triggered via push March 20, 2026 19:27
Status Success
Total duration 41m 21s
Artifacts 44

build.yml

on: push
Matrix: build-clang-cl
Matrix: build-linux
Matrix: build-msvc-arm
Matrix: build-msvc
Fit to window
Zoom out
Zoom in

Annotations

33 warnings
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, 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.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, 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, 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, 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, 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-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-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-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-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 (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/
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-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.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/
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-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-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-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-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, 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 (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, 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-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-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 (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, 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-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-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-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-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-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/

Artifacts

Produced during runtime
Name Size Digest
reactos-clang-amd64-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
459 MB
sha256:9f2932285258522fa71f98241c392a75888594464e68dd777a34ce35000533e9
reactos-clang-amd64-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
173 MB
sha256:d0b4ea155c81bfbb61c069a4d1ad03e3fc00268639736cddf388e7c9fc82bf0a
reactos-clang-cl-amd64-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
143 MB
sha256:2d5e54306aa019b7247e9e190be458435e1344e6a3f1f536ecea3fed2428a81f
reactos-clang-cl-amd64-Release-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
133 MB
sha256:bf37540e30cedc54b42074ac5f0bf84d7ff9b0d1e2b04fe6a438365fd2c37d2b
reactos-clang-cl-i386-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
145 MB
sha256:36c48a27e0fd849ffa62b363070317dabd0d56f812a77ee112b11a77a2b9adaf
reactos-clang-cl-i386-Release-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
132 MB
sha256:3eaac111aeefd12c88f59d412782299214f4915a1424c78d2cb253443f1f8038
reactos-clang-i386-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
215 MB
sha256:a306cfdd2b204b32a7ec0f473c29254c3d83f6974526db7f95a73c250ab809b7
reactos-clang-i386-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
172 MB
sha256:12042dee753800db17cd600688ffd05005016a038dd1af8ac44a9ede3db33b5f
reactos-gcc-amd64-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
427 MB
sha256:cadc769f12368bdcd281ceaa3d6901ff11f04e23607032aff9824ee0a321ed67
reactos-gcc-amd64-Debug-0x600-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
427 MB
sha256:700eae21ac375dc27f6004b502a31807ad7fee9f37e9536ce4a03c710f90f43b
reactos-gcc-amd64-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
177 MB
sha256:c84182faacc1b6b127b12f8fa1e24c704ff2eb6a1e9590e7153d956b716d119a
reactos-gcc-i386-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
206 MB
sha256:35142e25055e9df86a66cc796fea645a44e6441ed96cb43772a1aaa9cc95fcdb
reactos-gcc-i386-Debug-0x600-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
207 MB
sha256:2c4acab6d511c237db4bab9d86f8ccd6a2ea48fc6356f11519010e8d98391bcf
reactos-gcc-i386-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
192 MB
sha256:adc3bc89aaddad21e4bc351118da519851bc8c2ab6bdb7a2f67160f0cc55ffe3
reactos-msvc14-amd64-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
150 MB
sha256:545eda078105130fc41cbfceca16590b486d123b91c493c7f18650baeb9f0dac
reactos-msvc14-amd64-Debug-0x600-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
150 MB
sha256:f081cc494ddd7cd818fb006ff8f9ece415da5306d0a98992c610a3219ff0193f
reactos-msvc14-amd64-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
138 MB
sha256:a60e731377b01b3c27bd9f24e687adaed2e6790334e52ac39ace8f2330800da4
reactos-msvc14-arm-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
12.7 MB
sha256:04d8fc60ffb1d97ec0dd9df0a1107f55b73299842092e6e12fd4ed49653d26af
reactos-msvc14-arm-Release-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
10.8 MB
sha256:1873cf2793574aadda1c627c184f8b935a2f4f4cbf9e2bdcab3aa323c5b1fd39
reactos-msvc14-arm64-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
3.2 MB
sha256:0126030f5e7728ad3df414bc9f364296ccc7d0e15c3ea7e531283eea188d13a9
reactos-msvc14-arm64-Release-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
3.09 MB
sha256:e621e3b5274a9403c5ace14bf5962eb030cb2247b0e91d3acd4813203b69cc89
reactos-msvc14-i386-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
154 MB
sha256:d7b8a7796c0c16b4f09d6e982002d35277cd1ef50b78757fe6bf6cc2604b490a
reactos-msvc14-i386-Debug-0x600-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
154 MB
sha256:226f5290e18ff1698818266d9738e034884d32d2c8415f1bd351ca75a268fcb4
reactos-msvc14-i386-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
131 MB
sha256:8779f0b5e971f1306f5fad142ba66c81beef2957971f334a2abc1e58deeeba71
reactos-msvc14.2-amd64-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
150 MB
sha256:6cbab203a3a59e63679c08fcf51737f92737079dc4131cb67f0d445f249090b6
reactos-msvc14.2-amd64-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
138 MB
sha256:154da4af2c8ccdc537c50bb40a3205a83bf37f6857e1395cb1b34a20b7b79ae5
reactos-msvc14.2-i386-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
154 MB
sha256:c69c18557f839b307cf4418b32d1030ef823693b62e323218825e2be5d9e6413
reactos-msvc14.2-i386-Release-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
130 MB
sha256:31d75d217d3760de3348f25d4b09b417cd2a4868dbf0bf6a6698245689cae391
reactos-msvc14.29-arm-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
12.7 MB
sha256:6278ac9ac3bcb0a21a6ac50907c150a609f63f141e195c6ef988493113fc264d
reactos-msvc14.29-arm-Release-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
10.7 MB
sha256:2a8dfe3fee60e5262788ec811b3def4a4af9171d51fef8cd656261c4cbd25ebd
reactos-msvc14.29-arm64-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
3.2 MB
sha256:730340a27b084f8bd1a6435503271118f5276a936338c6bda6e40af806144fbe
reactos-msvc14.29-arm64-Release-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
3.07 MB
sha256:ed135db367aad53755c4bf7a5945d78775d62ac84cfbb89075c7b97bc932e870
reactos-syms-clang-cl-amd64-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
103 MB
sha256:071b190d1208c00f8602cb8ee58974c4f75c4f3c446f3577a47794bc696b34ba
reactos-syms-clang-cl-i386-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
112 MB
sha256:00248840214c7d6023cff3cb14f0b560e26e76552efa88e631d9abb5fbe28b67
reactos-syms-msvc14-amd64-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
226 MB
sha256:6eb99052cec9823d93121f45a05e2d39a89c3ef5b711a3e04838de7125db2cca
reactos-syms-msvc14-amd64-Debug-0x600-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
226 MB
sha256:525662e76f3afffab51f06226efd04b334eaceb517031962c19f556a326fdf65
reactos-syms-msvc14-arm-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
54.7 MB
sha256:e226c2437739186fd14df1c530ef221a301eb04a3787e76fe3ba9115da5ee7de
reactos-syms-msvc14-arm64-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
7.72 MB
sha256:c726f98989807eca24057ea43e9e8204f1a7a07866fa07ac9a8c5e5a4ea64b67
reactos-syms-msvc14-i386-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
233 MB
sha256:d0081a677fcc6458c302489110c49836c9ad06b74e7f5921ec43f242da47f86d
reactos-syms-msvc14-i386-Debug-0x600-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
233 MB
sha256:a09294be7e068f9903ee3a6845092db7b25365f4d5644a44b505e475d2887d54
reactos-syms-msvc14.2-amd64-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
211 MB
sha256:5ec63df5e7b832df7cbbb7a57bb015ff53a889188608614ae17cd3a4c9ab83b7
reactos-syms-msvc14.2-i386-Debug-0x502-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
217 MB
sha256:aa47d940e9259f6024abe7287e78a34a53ea932a986fddba84b17b059ea5b91b
reactos-syms-msvc14.29-arm-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
50.4 MB
sha256:e43c4fc8907d5cbd711df6082eecb8e2bca33f4aeb9f4d24694f92214db8c628
reactos-syms-msvc14.29-arm64-Debug-1c2b5a1a8e1d681f5c71b80e08d989cac6548f22
7.33 MB
sha256:dead8f7e460d75f81d1816ccda9b7b53185f2d6fdea2e6bdfb21383e48981e6b