Skip to content

replay: add short-cut: when one merge parent is the same as before, fall #2209

replay: add short-cut: when one merge parent is the same as before, fall

replay: add short-cut: when one merge parent is the same as before, fall #2209

Triggered via push May 17, 2026 15:46
Status Failure
Total duration 35m 54s
Artifacts 4

main.yml

on: push
win+VS build
win+VS build
win+Meson build
4m 18s
win+Meson build
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Fit to window
Zoom out
Zoom in

Annotations

50 errors, 60 warnings, and 22 notices
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#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-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-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-sha256 (ubuntu:rolling): ident.c#L139
ident.c:139:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ident.c#L112
ident.c:112:33: '_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#L945
./git-compat-util.h:945:6: '_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): kwset.c#L556
kwset.c:556:12: '_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): ./refs.h#L537
./refs.h:537:9: '_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-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.11 previously-resolved conflicts with diff3
linux-leaks (ubuntu:rolling)
failed: t3454.10 file containing literal conflict-marker bytes survives a replay-merge
linux-leaks (ubuntu:rolling)
failed: t3454.9 vanishing conflict in a replayed merge
linux-leaks (ubuntu:rolling)
failed: t3454.8 newly-introduced binary conflict is reported
linux-leaks (ubuntu:rolling)
failed: t3454.7 newly-introduced conflict in a replayed merge
linux-leaks (ubuntu:rolling)
failed: t3454.6 preserves resolutions; does not extrapolate
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.11 previously-resolved conflicts with diff3
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.10 file containing literal conflict-marker bytes survives a replay-merge
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.9 vanishing conflict in a replayed merge
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.8 newly-introduced binary conflict is reported
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.7 newly-introduced conflict in a replayed merge
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.6 preserves resolutions; does not extrapolate
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/
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
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
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 (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.
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.
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
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.
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
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+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 (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 (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+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 (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 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 (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/
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+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 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/
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 (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 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 (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/
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
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/
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
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/
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/
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-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win build
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (0)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (1)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (3)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (2)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (5)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (6)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (7)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (9)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (6)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (8)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (1)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win+Meson test (4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (7)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (0)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (3)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (2)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (9)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
win test (5)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
failed-tests-linux-leaks
82.9 KB
sha256:ba2b3cdf9e2cf123599844c0a434ebacef9869636d5a028cc484912acd368e47
failed-tests-linux-reftable-leaks
86.5 KB
sha256:1d23480f73fca646ab9f623fc1e789b0a22964320379695f8f893b4198535b99
windows-artifacts
96.9 MB
sha256:747e625580c48dd3681c91a6b0c4136b42979aa4c3f5e1637e55a1fc280dec77
windows-meson-artifacts
56.9 MB
sha256:71617ab4751280e45295b247e9fb8bbe53a6071071f4ffd2d87d5eae995167c4