nightly #1230
nightly.yml
on: schedule
buildmgr
/
...
/
config
3s
buildmgr
/
coverage
4m 40s
buildmgr
/
docs
1m 9s
Matrix: buildmgr / build
Matrix: buildmgr / sanity-check-native
Matrix: buildmgr / sanity-check-docker
Matrix: buildmgr / test
Matrix: packchk / test
Matrix: packchk / build
Matrix: packgen / unittest
Matrix: packgen / build
Matrix: projmgr / unittest
Matrix: projmgr / build-swig
Matrix: projmgr / build
Matrix: svdconv / test
Matrix: svdconv / build
Matrix: test_libs / test_libs
coverage
32s
Annotations
2 errors and 140 warnings
|
projmgr / build-swig (macos-15-intel, amd64)
❌ Failed to install macOS agent: Error: Command failed: sudo "/opt/step-security/Installer" -workdir /opt/step-security >> /opt/step-security/agent.log 2>&1
|
|
svdconv / build (macos-15-intel, amd64)
❌ Failed to install macOS agent: Error: Command failed: sudo "/opt/step-security/Installer" -workdir /opt/step-security >> /opt/step-security/agent.log 2>&1
|
|
buildmgr / matrix_prep / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / build (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / build (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / build (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / build (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / build (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / build (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b, Wandalen/wretry.action@v3.8.0_js_action. 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/
|
|
buildmgr / create_installer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity check native (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity check native (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity check native (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity-check-docker (debian:buster)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity check native (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity check native (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / sanity check native (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (macos-14, arm64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
buildmgr / test (macos-14, arm64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
buildmgr / test (macos-14, arm64)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
|
buildmgr / test (macos-14, arm64)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
buildmgr / test (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
buildmgr / test (macos-15-intel, amd64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
buildmgr / test (macos-15-intel, amd64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
buildmgr / test (macos-15-intel, amd64)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
|
buildmgr / test (macos-15-intel, amd64)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
buildmgr / Publish Tests Results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / matrix_prep / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / build (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (macos-14, arm64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
packchk / test (macos-14, arm64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
packchk / test (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b, Wandalen/wretry.action@v3.8.0_js_action. 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/
|
|
packchk / build (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / build (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / build (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / test (macos-15-intel, amd64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
packchk / test (macos-15-intel, amd64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
packchk / Publish Tests Results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / build (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packchk / build (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / matrix_prep / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / unittest (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / unittest (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / unittest (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / build (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / build (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b, Wandalen/wretry.action@v3.8.0_js_action. 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/
|
|
packgen / build (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / unittest (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / unittest (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / build (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / unittest (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / Publish Tests Results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / build (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
packgen / build (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / matrix_prep / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build (macos-14,arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build (ubuntu-22.04,amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / unittest (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / unittest (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build (ubuntu-22.04,arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / unittest (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build (windows-2022,amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build (windows-2022,arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build (macos-15-intel,amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / unittest (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b, Wandalen/wretry.action@v3.8.0_js_action. 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/
|
|
projmgr / unittest (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / build-swig (macos-15-intel, amd64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
projmgr / build-swig (macos-15-intel, amd64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
projmgr / build-swig (macos-15-intel, amd64)
😭 macos agent installation failed
|
|
projmgr / unittest (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
projmgr / Publish Tests Results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / matrix_prep / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (macos-14, arm64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
svdconv / test (macos-14, arm64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
svdconv / build (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / build (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / build (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b, Wandalen/wretry.action@v3.8.0_js_action. 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/
|
|
svdconv / test (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>::pointer': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>::difference_type': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>::value_type': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>::iterator_category': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>::_Prevent_inheriting_unwrap': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, arm64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>::pointer': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>::difference_type': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>::value_type': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>::iterator_category': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>::_Prevent_inheriting_unwrap': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (windows-2022, amd64)
'stdext::checked_array_iterator<T *>': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
|
|
svdconv / test (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / test (macos-15-intel, amd64)
swig 4.4.1 is already installed and up-to-date.
To reinstall 4.4.1, run:
brew reinstall swig
|
|
svdconv / test (macos-15-intel, amd64)
doxygen 1.16.1 is already installed and up-to-date.
To reinstall 1.16.1, run:
brew reinstall doxygen
|
|
svdconv / Publish Tests Results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / build (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / build (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, ilammy/msvc-dev-cmd@v1, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / build (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
svdconv / build (macos-15-intel, amd64)
😭 macos agent installation failed
|
|
test_libs / matrix_prep / matrix_prep
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
|
|
test_libs / test_libs (macos-14, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master. 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/
|
|
test_libs / test_libs (macos-14, arm64)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
|
test_libs / test_libs (ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master. 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/
|
|
test_libs / test_libs (windows-2022, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, 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/
|
|
test_libs / test_libs (ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master. 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/
|
|
test_libs / test_libs (windows-2022, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@master, 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/
|
|
test_libs / test_libs (macos-15-intel, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@master. 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/
|
|
test_libs / test_libs (macos-15-intel, amd64)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
|
coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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 | |
|---|---|---|---|
|
Event File buildmgr
|
1.55 KB |
sha256:b4ae71351805de31d9114ddcb97e039fb5a698ac6460298b961894c6cd96ce7a
|
|
|
Event File packchk
|
1.55 KB |
sha256:9d740b989c0af9f68e34b3e04456ea7f46ef49c4a26e841889a870a9c2e11d6f
|
|
|
Event File packgen
|
1.55 KB |
sha256:9068b819989ae088aa3d6333019ab671c9965b582d220dbb152c71679332a0fc
|
|
|
Event File projmgr
|
1.55 KB |
sha256:979c722526509b4c82b47a11710408dd4324172c1267015d0eb8950045eddaf1
|
|
|
Event File svdconv
|
1.55 KB |
sha256:63da7cb8214b4a9cbbe6da721b63ad37842cfce4bc666ed079fd573c856077ea
|
|
|
Event File test_libs
|
1.55 KB |
sha256:0b0c10a9b00c8996df2d96915d7c06527fc06b431e08252b0a952973824bc59c
|
|
|
cbuild_install
Expired
|
83.4 MB |
sha256:0ad12727e42d22dddd63f975f08dc36abe8a771a2eefe9152b07e9cd58ef8bcd
|
|
|
cbuildgen-darwin-amd64
Expired
|
889 KB |
sha256:d8f54ffa95ceb0d1b33026b4c1b41c3d86801cc1c44db6bf5fc6bfc79151a8c9
|
|
|
cbuildgen-darwin-arm64
Expired
|
947 KB |
sha256:b9647a3dfa766c221aa3fe96978db427cc3c87e5b990b601183fef6fcb9dceb1
|
|
|
cbuildgen-linux-amd64
Expired
|
2.08 MB |
sha256:b3344198ad1109db8251ec16e3f61ebdd2762eed10ce9f6a50d21149349df354
|
|
|
cbuildgen-linux-arm64
Expired
|
1.93 MB |
sha256:f77cc377850e6d46a4dde2be474ed668084e42857769ff0768647051dd60b0a3
|
|
|
cbuildgen-windows-amd64
Expired
|
796 KB |
sha256:0e47bb323c1593f2971c53f9392cf6a7848c567da8efdce7af0034a44e9faf5e
|
|
|
cbuildgen-windows-arm64
Expired
|
755 KB |
sha256:e81184c27089f963899d0ebddd2ca65265ac2e2153c3e3e7ad5ef5cc247e1409
|
|
|
coverage-report-buildmgr
Expired
|
259 KB |
sha256:390066f66a5597c2aa3a466c09c3d90fff353488093c4b685134adf8f1577323
|
|
|
coverage-report-packchk
Expired
|
252 KB |
sha256:275ed145f93d520f0370a129cec0ccf701e3675eacc469383df6825a4db36a44
|
|
|
coverage-report-packgen
Expired
|
49.2 KB |
sha256:2fd538183b96d8463b06a295f7fa99a62ed847b49a4b0ca78acb0389ba2e44b2
|
|
|
coverage-report-projmgr
Expired
|
538 KB |
sha256:f990ac122c352c7bc65cc3e2590b6a10a295a618729c43ca3ed73804963c4499
|
|
|
coverage-report-svdconv
Expired
|
773 KB |
sha256:92657f2c18ae8a775598fe92f506bc2ff06a5af84bf88b93f1568d5294dadfb6
|
|
|
deb_package
Expired
|
12.6 MB |
sha256:c914229707226ffd10bfc5a7bb3dcceb641f4ce5bc0a8121da8edeb5596ae4e2
|
|
|
documentation
Expired
|
234 KB |
sha256:89606b2737b828e8ce7ac8209fc8d9e45ee1baafdc165a3dbcdc6660da6de80f
|
|
|
integ_test_result_buildmgr-darwin-amd64
Expired
|
3.7 KB |
sha256:a743b5d688a02134eea965659a1ea1b1085dea8ca206f031592dd5c5c7595c8c
|
|
|
integ_test_result_buildmgr-linux-amd64
Expired
|
3.66 KB |
sha256:7ff86a21300b1c09cef56dcb3e280a7c316a93bc6c8ce268a860081b36c01c97
|
|
|
integ_test_result_buildmgr-linux-arm64
Expired
|
3.71 KB |
sha256:a15600046f1a2830ddc9658aff385898aa80724dc3d8a57cd0b83c300cf8d0cf
|
|
|
integ_test_result_buildmgr-windows-amd64
Expired
|
3.7 KB |
sha256:78258604a4d3d0214775b899eaf8c727277554fc34027ed9a7d214a622c706a2
|
|
|
integ_test_result_packchk-darwin-amd64
Expired
|
1.36 KB |
sha256:d7fd5b88b075395b80ff0ddbde59c8d163484bb5c941fd3559fbb37dae0c4817
|
|
|
integ_test_result_packchk-linux-amd64
Expired
|
1.36 KB |
sha256:ff4857093b74a2ad711994851aaf42c7a2c9c7643bb00eca50cf7add292246ea
|
|
|
integ_test_result_packchk-windows-amd64
Expired
|
1.39 KB |
sha256:345e9f0ef9bd12b52902e1e8460c6e09ccc1518ca4c1ca1669005b5cec2e6512
|
|
|
integ_test_result_svdconv-darwin-amd64
Expired
|
871 Bytes |
sha256:7344ad4aa1b3b1640407f02a8457ba33cb3d32ffd48921dd8b0e3e15e1f3ead3
|
|
|
integ_test_result_svdconv-linux-amd64
Expired
|
854 Bytes |
sha256:762e9f6c5d07db118f3cc26b3bdd2e50daaa54c9f8064d7aa1fef80eb08d45da
|
|
|
integ_test_result_svdconv-windows-amd64
Expired
|
898 Bytes |
sha256:a9858fc1898c833eceff1058f5b6f6e663389d4f64f29c0a7ae74220420c5537
|
|
|
merged-coverage-report
|
254 KB |
sha256:8ec7afc50bd06a58a59d65944da6013acbb70a83297c4df7fd0bddfc58a40c70
|
|
|
packchk-darwin-amd64
Expired
|
1.77 MB |
sha256:919692b770092a73240ff5305b1c62bc705cb210d594a631a3bb50d7ffc4e1e8
|
|
|
packchk-darwin-arm64
Expired
|
1.81 MB |
sha256:028ffde57a9aafe92fe7c71280a5b5e06e3793559a93ce19a322f4c1a717b3fc
|
|
|
packchk-linux-amd64
Expired
|
2.76 MB |
sha256:508af4e2fd52781ab638c1737fc9122728ffcd1a2bd16c4365a5cf82929d4507
|
|
|
packchk-linux-arm64
Expired
|
2.53 MB |
sha256:4bfec5117054ee3ea4530829b43692a1bacdece39ca6f51a065a5aaf3c951417
|
|
|
packchk-windows-amd64
Expired
|
1.43 MB |
sha256:9402ad5b0befc996cf0b7c9f852916dec7adf922c0a9f89ff86bb246cad96c61
|
|
|
packchk-windows-arm64
Expired
|
1.38 MB |
sha256:6104d2e85cc1bf7025997035f6c6629989687be43dd40a8f53b01ecd853d6004
|
|
|
packgen-darwin-amd64
Expired
|
496 KB |
sha256:d1ae361e3e08e5f1410dff1dc299689bd48c367d89e883dfd4209de98eee5a29
|
|
|
packgen-darwin-arm64
Expired
|
545 KB |
sha256:cadc1e185f8814ef9a36f450daf3e3cde7797de017677084e9a47ec8f827c396
|
|
|
packgen-linux-amd64
Expired
|
1.49 MB |
sha256:33b6909f9e2c657f03fc42a59cac87b3154bdb2b639c2a4f915f4f180b9699af
|
|
|
packgen-linux-arm64
Expired
|
1.37 MB |
sha256:e707f02ddd19fed62c848a2d2ed99a88e358a2a92961ba6e4ad82c0e8f27cd00
|
|
|
packgen-windows-amd64
Expired
|
470 KB |
sha256:4bc718c6358bea03e8ec09eed0d868c462c3f5dc5e784ca3304cfa2074767d45
|
|
|
packgen-windows-arm64
Expired
|
435 KB |
sha256:5e6b71b4b3f806fcf7dccf633e98794f517e663e25ce220108d10c6a8824d92d
|
|
|
projmgr-darwin-amd64
Expired
|
1.84 MB |
sha256:59b26ff9ea0a3c98ad2dfc56e965422cad1959bf8de843fd0d68fba86f9e45c7
|
|
|
projmgr-darwin-arm64
Expired
|
1.98 MB |
sha256:5286b9f8b52fc4ac3fec9e33323d3600ee4f2449f07823a74c835c9b7b90fd7f
|
|
|
projmgr-linux-amd64
Expired
|
3.34 MB |
sha256:c4d46a3a48c843fe38e36fc447974279dac59d24f07505c2da2062657106968f
|
|
|
projmgr-linux-arm64
Expired
|
3.16 MB |
sha256:a33e79d4c53ac17dedd7f90de2b6774ddac3b05ad21e1eca6210761b4c855c91
|
|
|
projmgr-schemas
Expired
|
24 KB |
sha256:9f861ff4f283cb4a470b7fe574087c6393b52579ab1c47d19aa567643ddb5acb
|
|
|
projmgr-swig-go-darwin-amd64
Expired
|
1.94 MB |
sha256:5fd4e28d05aa6a1f3bf84b4f0e7a2df63f21d8345f0e60785b1a6d59a2ea6596
|
|
|
projmgr-swig-go-linux-amd64
Expired
|
3.13 MB |
sha256:a0fd36e9b837a5d2a0604ddfe034c3a6e8513ce674e2cb648bed5653d7717f68
|
|
|
projmgr-swig-python-darwin-amd64
Expired
|
2.06 MB |
sha256:f9413c1abd75350b432d3d7aa5b69c6ece0d79488660b789dcea2a2a4c2c35f4
|
|
|
projmgr-swig-python-linux-amd64
Expired
|
3.26 MB |
sha256:a8c8c76b5fc20979bebc4d8e5f48e94fc694f9e332603b2fd571651e746db798
|
|
|
projmgr-swig-python-windows-amd64
Expired
|
1.7 MB |
sha256:d0bcbfe08f5af2a5c69586ac5ba43e15c436f63180eb8a52c3d994cf13f70220
|
|
|
projmgr-templates
Expired
|
13.4 KB |
sha256:c6bacbb83d5d6477afc64e43c7c1d99ceaf6f5a2a25930eb34f4bcc5405d2abb
|
|
|
projmgr-windows-amd64
Expired
|
1.46 MB |
sha256:775b9327eef5e1aeb13cc9df998364dee2d19901a3359d24e80be143d88ea7fc
|
|
|
projmgr-windows-arm64
Expired
|
1.41 MB |
sha256:368f7cc03d80698757c5d086e49fbd9495ade4ce4499650c2b38eb3c2cd16f4c
|
|
|
svdconv-darwin-amd64
Expired
|
675 KB |
sha256:f2f436ae7ebd9c8b4d6c565ebf3de454930016a9cda5362cf38ff49acb03930a
|
|
|
svdconv-darwin-arm64
Expired
|
674 KB |
sha256:1748dea77dfe524a44dd6125bf75f82a7699480836857c4e09063ce8f3c79364
|
|
|
svdconv-linux-amd64
Expired
|
1.64 MB |
sha256:1647cbcabd94511adb1afef4c888b7f97afdff6e4eefb58adb0c98c5a3d052a7
|
|
|
svdconv-linux-arm64
Expired
|
1.5 MB |
sha256:3d9cdeb48b328cd45204c40df3b678e32022b905cd6ef596bb3da63f8344d0b6
|
|
|
svdconv-windows-amd64
Expired
|
616 KB |
sha256:ba44c5d958d34ffedcb0c7f2da8233a0999caa31f8a9c344728bb97b94c6df4f
|
|
|
svdconv-windows-arm64
Expired
|
586 KB |
sha256:c4b51c0df6fda218b801c011466b85cd930501d0029a9d06ba07a573d6097509
|
|
|
unit_test_result_buildmgr-darwin-amd64
Expired
|
1.35 KB |
sha256:80a5936745ba9a57c2004f55df50c1b0ea79ecf3a74fe81359ee2427e6cae549
|
|
|
unit_test_result_buildmgr-linux-amd64
Expired
|
1.31 KB |
sha256:a04132ebfa1b5df984eba0031b2b0f706cbef2d733aca0b5e9168854bcd0efe4
|
|
|
unit_test_result_buildmgr-windows-amd64
Expired
|
1.38 KB |
sha256:8c8748a59b4c9ebb93df130e57ed2ab185e530715f7474a75af8585669a1ff9f
|
|
|
unit_test_result_packchk-darwin-amd64
Expired
|
662 Bytes |
sha256:8a32accd74fd5bdcab7318c4274dc2817e6677d1f0864219018fa431d9e2b1b3
|
|
|
unit_test_result_packchk-linux-amd64
Expired
|
652 Bytes |
sha256:3dc86403666e84ac44deded40d53a50c2d0fd0843424f13cd4112de21bfc9db8
|
|
|
unit_test_result_packchk-windows-amd64
Expired
|
659 Bytes |
sha256:3bf9b3dda9411506444f3323a06b01d62aaa53214c79c448d727081579a1a416
|
|
|
unit_test_result_packgen-darwin-amd64
Expired
|
769 Bytes |
sha256:cfdfb84247cc4f83f044da213f38e64635b9c287baad53b379e4a06795599c79
|
|
|
unit_test_result_packgen-linux-amd64
Expired
|
777 Bytes |
sha256:de34d2f444ab53c09b4fbc48ff72a7be4b6e7a4e0ca0e76ebec890ea5c9d6f0a
|
|
|
unit_test_result_packgen-windows-amd64
Expired
|
779 Bytes |
sha256:90336e1bc680d00ef5cc8e9675cf3378003f64fcec34d0e97a0416ebde64493f
|
|
|
unit_test_result_projmgr-darwin-amd64
Expired
|
10.6 KB |
sha256:199ff2098ac7e16a3e37a96dd6d81c442b0c329479329fc7c6d7be18ff14799c
|
|
|
unit_test_result_projmgr-linux-amd64
Expired
|
10.3 KB |
sha256:2463ea9c109e7fa6c066abd017e5782b76dc93367f909778e5f536147f93a763
|
|
|
unit_test_result_projmgr-windows-amd64
Expired
|
10.8 KB |
sha256:aff3f39f71fd0049a4133fa20554e554d0f058c527963b02c44c2e5e049cd3ed
|
|
|
unit_test_result_svdconv-darwin-amd64
Expired
|
676 Bytes |
sha256:fe489fa4b416ae6fb9434228600282e10c320bd6f2b9152551a8cd6ab97ec543
|
|
|
unit_test_result_svdconv-linux-amd64
Expired
|
676 Bytes |
sha256:432c3ce05987cb9f7d76595ed7d3214186087281da008026d419f1223f80779d
|
|
|
unit_test_result_svdconv-windows-amd64
Expired
|
683 Bytes |
sha256:f679b4785d391ae0b731afc99c37a81be8b62b5c7f9c64f7fa72e19559b67d0c
|
|
|
unit_test_result_test_libs-darwin-amd64
Expired
|
8.07 KB |
sha256:c40a577e3ede2624a7bed683065ca77d9e6f8f24566f22daa1f54abf92546f66
|
|
|
unit_test_result_test_libs-linux-amd64
Expired
|
7.81 KB |
sha256:7d504f88929a8a7cdb160fdd3308b2d5e8cff57d4f363d288378f23322bd490e
|
|
|
unit_test_result_test_libs-windows-amd64
Expired
|
7.96 KB |
sha256:73355b8ffbebdd05f1555df927529d72e99b47162d89072b051bbf657d4e173a
|
|
|
unittest-darwin-amd64
Expired
|
20.2 KB |
sha256:736b706acbeb25cef7a5b83f5637a94331510b6548aeb4f509a1629c6283eca9
|
|
|
unittest-linux-amd64
Expired
|
20 KB |
sha256:d052dac4ed8c123a82cb100351cde23f10a197098e4cb1f59603bc879f59d33e
|
|
|
unittest-windows-amd64
Expired
|
20.2 KB |
sha256:dca18698f29b751ddaed8818e6902b618dc4b535ffe7961b3b7dfc2ba453f1be
|
|