CI #27053
gitgitgadget[bot]main.yml
on: push
config
6s
fuzz smoke test
1m 13s
static-analysis
5m 14s
rust-analysis
1m 46s
sparse
3m 28s
documentation
7m 29s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
196 errors and 77 warnings
|
linux-sha256 (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-sha256 (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
osx-gcc (macos-14)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
osx-gcc (macos-14)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
osx-gcc (macos-14)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
osx-gcc (macos-14)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
osx-gcc (macos-14)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
osx-gcc (macos-14)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
osx-gcc (macos-14)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
osx-gcc (macos-14)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
osx-gcc (macos-14)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
osx-gcc (macos-14)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-meson (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-meson (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-meson (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-meson (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-meson (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-meson (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-meson (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-meson (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-meson (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-meson (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
osx-clang (macos-14)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
osx-clang (macos-14)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
osx-clang (macos-14)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
osx-clang (macos-14)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
osx-clang (macos-14)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
osx-clang (macos-14)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
osx-clang (macos-14)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
osx-clang (macos-14)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
osx-clang (macos-14)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
osx-clang (macos-14)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
|
|
linux-musl-meson (alpine:latest)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-musl-meson (alpine:latest)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-musl-meson (alpine:latest)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-musl-meson (alpine:latest)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-musl-meson (alpine:latest)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-musl-meson (alpine:latest)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-musl-meson (alpine:latest)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-musl-meson (alpine:latest)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-musl-meson (alpine:latest)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-musl-meson (alpine:latest)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
osx-reftable (macos-14)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
osx-reftable (macos-14)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
osx-reftable (macos-14)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
osx-reftable (macos-14)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
osx-reftable (macos-14)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
osx-reftable (macos-14)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
osx-reftable (macos-14)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
osx-reftable (macos-14)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
osx-reftable (macos-14)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
osx-reftable (macos-14)
failed: t1800.57 parallel hook output is not interleaved
|
|
osx-meson (macos-14)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
osx-meson (macos-14)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
osx-meson (macos-14)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
osx-meson (macos-14)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
osx-meson (macos-14)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
osx-meson (macos-14)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
osx-meson (macos-14)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
osx-meson (macos-14)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
osx-meson (macos-14)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
osx-meson (macos-14)
failed: t1800.57 parallel hook output is not interleaved
|
|
almalinux-8 (almalinux:8)
Process completed with exit code 1.
|
|
almalinux-8 (almalinux:8)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
almalinux-8 (almalinux:8)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
almalinux-8 (almalinux:8)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
almalinux-8 (almalinux:8)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
almalinux-8 (almalinux:8)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
almalinux-8 (almalinux:8)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
almalinux-8 (almalinux:8)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
almalinux-8 (almalinux:8)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
almalinux-8 (almalinux:8)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
almalinux-8 (almalinux:8)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-reftable (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux32 (i386/ubuntu:focal)
failed: t1800.57 parallel hook output is not interleaved
|
|
debian-11 (debian:11)
Process completed with exit code 2.
|
|
debian-11 (debian:11)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
debian-11 (debian:11)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
debian-11 (debian:11)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
debian-11 (debian:11)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
debian-11 (debian:11)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
debian-11 (debian:11)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
debian-11 (debian:11)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
debian-11 (debian:11)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
debian-11 (debian:11)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
debian-11 (debian:11)
failed: t1800.57 parallel hook output is not interleaved
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
linux-leaks (ubuntu:rolling)
failed: t1800.57 parallel hook output is not interleaved
|
|
win+Meson test (2)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
win+Meson test (2)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
win+Meson test (2)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
win+Meson test (2)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
win+Meson test (2)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
win+Meson test (2)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
win+Meson test (2)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
win+Meson test (2)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
win+Meson test (2)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
win+Meson test (2)
failed: t1800.57 parallel hook output is not interleaved
|
|
win test (8)
failed: t1800.66 one non-parallel hook forces the whole event to run serially
|
|
win test (8)
failed: t1800.65 hook.<name>.parallel=false (default) forces serial execution
|
|
win test (8)
failed: t1800.64 hook.<name>.parallel=true enables parallel execution
|
|
win test (8)
failed: t1800.63 hook.jobs=2 config runs hooks in parallel
|
|
win test (8)
failed: t1800.62 hook.jobs=1 config runs hooks in series
|
|
win test (8)
failed: t1800.61 git hook run -j2 warns for hooks not marked parallel=true
|
|
win test (8)
failed: t1800.60 git hook run -j2 overrides parallel=false
|
|
win test (8)
failed: t1800.59 git hook run -j2 runs hooks in parallel
|
|
win test (8)
failed: t1800.58 git hook run -j1 runs hooks in series
|
|
win test (8)
failed: t1800.57 parallel hook output is not interleaved
|
|
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. 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. 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/
|
|
rust-analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
linux-sha256 (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. 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-TEST-vars (ubuntu:20.04)
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-breaking-changes (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/
|
|
osx-gcc (macos-14)
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. 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-asan-ubsan (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. 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/
|
|
fedora-breaking-changes-meson (fedora:latest)
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/
|
|
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
|
|
linux-meson (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/
|
|
osx-clang (macos-14)
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. 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
|
|
linux-musl-meson (alpine:latest)
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. 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
|
|
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. 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)
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. 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
|
|
osx-meson (macos-14)
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. 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
|
|
almalinux-8 (almalinux:8)
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. 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/
|
|
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
|
|
linux-reftable (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. 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)
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. 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
|
|
debian-11 (debian:11)
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. 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/
|
|
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
|
|
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. 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)
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. 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 (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. 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. 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 (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. 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 (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. 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 (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. 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 (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. 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 (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. 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 (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/upload-artifact@v4. 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/
|
|
win+Meson test (2)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
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. 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 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. 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 (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. 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. 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, 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. 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. 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. 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 (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. 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. 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. 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. 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 | |
|---|---|---|---|
|
failed-tests-almalinux-8
|
57.4 KB |
sha256:b12ed7b1c2550ebf68f96571ba751738312625a853316f6454a32d59c64fb574
|
|
|
failed-tests-debian-11
|
56.6 KB |
sha256:4d6e61e489f261e862c66e3315ca93e9a60398029561f279c72f95ab0bb9d856
|
|
|
failed-tests-fedora-breaking-changes-meson
|
54.2 KB |
sha256:55e3b6c27af1d9ffda051dd88d6d326c206b098ba2987bdee90f7fe1aba7eb07
|
|
|
failed-tests-linux-TEST-vars
|
58.1 KB |
sha256:4ce0f357ccc3d843b56eec7b8d1201869aec104c5c5a9d5f2ef704d75a39ef34
|
|
|
failed-tests-linux-asan-ubsan
|
56.8 KB |
sha256:b5d2d19f7c8359701d174d46eca453c192adbfa91143ff65f21a20af4199f23c
|
|
|
failed-tests-linux-breaking-changes
|
59.5 KB |
sha256:fba5f37c9d89e9cd0972467533ab2f8f32de4bd5215bcbdb0c306799da5f710b
|
|
|
failed-tests-linux-leaks
|
57.3 KB |
sha256:02060948a9eb638db40a0de69d74e55f4878c40217fea3317843bef4c09f6826
|
|
|
failed-tests-linux-meson
|
54.5 KB |
sha256:26a04442dbad881abc063a1daf01f67f40e094b813e827e2b24dc0f219d90729
|
|
|
failed-tests-linux-musl-meson
|
56.3 KB |
sha256:537b2608c5e89a7de4db58061108c5416b9136f7fc532723d712431ac88de312
|
|
|
failed-tests-linux-reftable
|
56.7 KB |
sha256:692272629f625996009b4e0b7b9f2d33ba67a46e59ccbd4abc53aed8f34a01d0
|
|
|
failed-tests-linux-reftable-leaks
|
58.7 KB |
sha256:05a2be1fdad02352dfe386d4e5d1d06c9ac4918fdafe2cf86b3c203b01eefbaa
|
|
|
failed-tests-linux-sha256
|
60.8 KB |
sha256:1091f8e9a93dcf20cef78fe2130b42d3e81138ee5066ec90e73011ffd8a2736b
|
|
|
failed-tests-linux32
|
57.3 KB |
sha256:0e17a4e9e56d8db5dd7a0f3390f08b9d22b6e31b60d6b885f874e2ef11f38d45
|
|
|
failed-tests-osx-clang
|
57.5 KB |
sha256:0ddaf7bfc41a805165284db56f35b000608f01f659eeb84972fb2a3ef34be605
|
|
|
failed-tests-osx-gcc
|
55.9 KB |
sha256:000af431b809ae358d46bcf5d19e246c228bc171c7622e472b7d247191afcb76
|
|
|
failed-tests-osx-meson
|
57.6 KB |
sha256:7988a7eabd5b242cfcb106ce2d35a163c01689d6284e2a824e3a89f0afc90d70
|
|
|
failed-tests-osx-reftable
|
58.6 KB |
sha256:111d1fc8022826769940aee3bd559c474216063bee18388d991c10043bb1b0aa
|
|
|
failed-tests-windows-8
|
54.9 KB |
sha256:aa87a4a6eab86f58602788e3d25fd1108467780460f8f3259472a541dafa1a3f
|
|
|
windows-artifacts
|
96.1 MB |
sha256:b9ec4d8d0ca3f8a3a5667199c69d97af5c26ef2d1e210623bfd0feee3a6e1d8b
|
|
|
windows-meson-artifacts
|
47.3 MB |
sha256:76091e97ff8dae58a1fa0c7eb29c1a0da344cdf2e854d5173091fe6a84685f29
|
|