replay: support replaying 2-parent merges #27634
dschomain.yml
on: pull_request
config
7s
fuzz smoke test
1m 3s
static-analysis
13m 17s
rust-analysis
1m 29s
sparse
3m 35s
documentation
9m 29s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
50 errors, 60 warnings, and 22 notices
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
cache-tree.c#L375
cache-tree.c:375:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling)
:321:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-sha256 (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
ident.c#L139
ident.c:139:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
ident.c#L112
ident.c:112:33: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-reftable (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
ident.c#L139
ident.c:139:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
ident.c#L112
ident.c:112:33: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-asan-ubsan (ubuntu:rolling):
./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.17 using replay on bare repo to perform basic cherry-pick
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.16 using replay to perform basic cherry-pick
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.15 using replay on bare repo to rebase with a conflict
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.14 using replay to rebase with a conflict
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.13 using replay on bare repo to rebase two branches, one on top of other
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.12 using replay to rebase two branches, one on top of other
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.11 reverting a merge commit is rejected
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.10 replaying an octopus merge is rejected
|
|
linux-leaks (ubuntu:rolling)
failed: t3650.9 using replay to rebase a 2-parent merge
|
|
linux-leaks (ubuntu:rolling)
failed: t3454.6 preserves manual rename of pre-existing caller; does not extrapolate to new files
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.17 using replay on bare repo to perform basic cherry-pick
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.16 using replay to perform basic cherry-pick
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.15 using replay on bare repo to rebase with a conflict
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.14 using replay to rebase with a conflict
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.13 using replay on bare repo to rebase two branches, one on top of other
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.12 using replay to rebase two branches, one on top of other
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.11 reverting a merge commit is rejected
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.10 replaying an octopus merge is rejected
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.9 using replay to rebase a 2-parent merge
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.6 preserves manual rename of pre-existing caller; does not extrapolate to new files
|
|
win+Meson build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-musl-meson (alpine:latest)
JGit wasn't installed, see above for clues why
|
|
linux-musl-meson (alpine:latest)
git-lfs wasn't installed, see above for clues why
|
|
linux-musl-meson (alpine:latest)
perforce wasn't installed, see above for clues why
|
|
debian-11 (debian:11)
JGit wasn't installed, see above for clues why
|
|
debian-11 (debian:11)
git-lfs wasn't installed, see above for clues why
|
|
debian-11 (debian:11)
perforce wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
JGit wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
git-lfs wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
perforce wasn't installed, see above for clues why
|
|
linux32 (i386/ubuntu:focal)
JGit wasn't installed, see above for clues why
|
|
linux32 (i386/ubuntu:focal)
git-lfs wasn't installed, see above for clues why
|
|
linux32 (i386/ubuntu:focal)
perforce wasn't installed, see above for clues why
|
|
almalinux-8 (almalinux:8)
JGit wasn't installed, see above for clues why
|
|
almalinux-8 (almalinux:8)
git-lfs wasn't installed, see above for clues why
|
|
almalinux-8 (almalinux:8)
perforce wasn't installed, see above for clues why
|
|
win+Meson test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (2)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (9)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
osx-clang (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-clang (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-meson (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-meson (macos-14)
pcre2 10.47_1 is already installed and up-to-date.
To reinstall 10.47_1, run:
brew reinstall pcre2
|
|
osx-meson (macos-14)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
osx-meson (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win+Meson test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-reftable (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-reftable (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
osx-gcc (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-gcc (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
linux-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-reftable-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
win+Meson build
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win build
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (5)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (4)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (2)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (1)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (8)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (9)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (7)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (6)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (3)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (3)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (4)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (7)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (8)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win+Meson test (6)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (1)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (9)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (5)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
win test (2)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
failed-tests-linux-leaks
|
78.6 KB |
sha256:b74475dc56e57b8b9a347ab24f4772c9d6b727ad1ac87c820661797c5dc11743
|
|
|
failed-tests-linux-reftable-leaks
|
81.8 KB |
sha256:a7027092c65e741c19ddbcb877991f975d99e342d487e3485ac97cbf58c214a6
|
|
|
windows-artifacts
|
96.9 MB |
sha256:94f20bdd079a013e58af68b8a43793611f22489fbe707a50a2450704cbc3e14a
|
|
|
windows-meson-artifacts
|
56.8 MB |
sha256:138d39385e306a16da8c647e181bd0f8349ed3cf71d59ea864a3d4c79953d8d9
|
|