Skip to content

t: detect errors outside of test cases #20

t: detect errors outside of test cases

t: detect errors outside of test cases #20

Triggered via push April 15, 2026 06:56
Status Failure
Total duration 33m 28s
Artifacts 13

main.yml

on: push
win+VS build
win+VS build
win+Meson build
3m 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

114 errors and 70 warnings
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
linux-musl-meson (alpine:latest)
failed: t0000.14 subtest: --verbose-only option
linux-musl-meson (alpine:latest)
failed: t0000.13 subtest: --verbose option
linux-musl-meson (alpine:latest)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-musl-meson (alpine:latest)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-musl-meson (alpine:latest)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-musl-meson (alpine:latest)
failed: t0000.9 subtest: a passing TODO test
linux-musl-meson (alpine:latest)
failed: t0000.8 subtest: a failing TODO test
linux-musl-meson (alpine:latest)
failed: t0000.7 subtest: --immediate
linux-musl-meson (alpine:latest)
failed: t0000.6 subtest: 2/3 tests passing
linux-musl-meson (alpine:latest)
failed: t0000.5 subtest: 3 passing tests
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
linux32 (i386/ubuntu:focal)
failed: t0000.14 subtest: --verbose-only option
linux32 (i386/ubuntu:focal)
failed: t0000.13 subtest: --verbose option
linux32 (i386/ubuntu:focal)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux32 (i386/ubuntu:focal)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux32 (i386/ubuntu:focal)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux32 (i386/ubuntu:focal)
failed: t0000.9 subtest: a passing TODO test
linux32 (i386/ubuntu:focal)
failed: t0000.8 subtest: a failing TODO test
linux32 (i386/ubuntu:focal)
failed: t0000.7 subtest: --immediate
linux32 (i386/ubuntu:focal)
failed: t0000.6 subtest: 2/3 tests passing
linux32 (i386/ubuntu:focal)
failed: t0000.5 subtest: 3 passing tests
debian-11 (debian:11)
Process completed with exit code 2.
debian-11 (debian:11)
failed: t0000.14 subtest: --verbose-only option
debian-11 (debian:11)
failed: t0000.13 subtest: --verbose option
debian-11 (debian:11)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
debian-11 (debian:11)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
debian-11 (debian:11)
failed: t0000.10 subtest: 2 TODO tests, one passin
debian-11 (debian:11)
failed: t0000.9 subtest: a passing TODO test
debian-11 (debian:11)
failed: t0000.8 subtest: a failing TODO test
debian-11 (debian:11)
failed: t0000.7 subtest: --immediate
debian-11 (debian:11)
failed: t0000.6 subtest: 2/3 tests passing
debian-11 (debian:11)
failed: t0000.5 subtest: 3 passing tests
linux-breaking-changes (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-breaking-changes (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-breaking-changes (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-breaking-changes (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-breaking-changes (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-breaking-changes (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-breaking-changes (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-breaking-changes (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-breaking-changes (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-breaking-changes (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
linux-TEST-vars (ubuntu:20.04)
failed: t0000.14 subtest: --verbose-only option
linux-TEST-vars (ubuntu:20.04)
failed: t0000.13 subtest: --verbose option
linux-TEST-vars (ubuntu:20.04)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-TEST-vars (ubuntu:20.04)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-TEST-vars (ubuntu:20.04)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-TEST-vars (ubuntu:20.04)
failed: t0000.9 subtest: a passing TODO test
linux-TEST-vars (ubuntu:20.04)
failed: t0000.8 subtest: a failing TODO test
linux-TEST-vars (ubuntu:20.04)
failed: t0000.7 subtest: --immediate
linux-TEST-vars (ubuntu:20.04)
failed: t0000.6 subtest: 2/3 tests passing
linux-TEST-vars (ubuntu:20.04)
failed: t0000.5 subtest: 3 passing tests
linux-reftable (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-reftable (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-reftable (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-reftable (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-reftable (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-reftable (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-reftable (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-reftable (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-reftable (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-reftable (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
linux-sha256 (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-sha256 (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-sha256 (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-sha256 (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-sha256 (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-sha256 (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-sha256 (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-sha256 (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-sha256 (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-sha256 (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
linux-meson (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-meson (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-meson (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-meson (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-meson (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-meson (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-meson (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-meson (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-meson (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-meson (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
linux-leaks (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-leaks (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-leaks (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-leaks (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-leaks (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-leaks (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-leaks (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-leaks (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-leaks (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-leaks (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-reftable-leaks (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.14 subtest: --verbose-only option
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.13 subtest: --verbose option
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.12 subtest: mixed results: a mixture of all possible results
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.11 subtest: mixed results: pass, failure and a TODO test
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.10 subtest: 2 TODO tests, one passin
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.9 subtest: a passing TODO test
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.8 subtest: a failing TODO test
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.7 subtest: --immediate
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.6 subtest: 2/3 tests passing
linux-asan-ubsan (ubuntu:rolling)
failed: t0000.5 subtest: 3 passing tests
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. 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
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)
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-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
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. 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
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
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. 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/
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
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/
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-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. 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+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 (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 (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.
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. 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-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/
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.
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+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 (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 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+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 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 (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 (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 (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+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+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 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/
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/
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/
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
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 (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/
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 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-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. 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/

Artifacts

Produced during runtime
Name Size Digest
failed-tests-debian-11
99.6 KB
sha256:344639128e6a86583081c39f0d6149c052e42742bfdfc2e8c382f44d61ff02f1
failed-tests-linux-TEST-vars
96.2 KB
sha256:df9f5edc726db2c7e839e12aee09932cd5039d3ded73d831f5f813657dfe4c09
failed-tests-linux-asan-ubsan
99.4 KB
sha256:31c6e479c152e56e4a4cc706a9c0e21d3a1880f3c8048da2ac23f08e55153fca
failed-tests-linux-breaking-changes
102 KB
sha256:d0569967c1ef5b77851b0f6d0fa09c7510116a4e2357a0620dc3a7957f368143
failed-tests-linux-leaks
97.1 KB
sha256:4524a67e89a2667cc012964dbf6165dee817a26e230ecf2d5d15680d2c77a69f
failed-tests-linux-meson
97.7 KB
sha256:79bb8ef014a182b3111693b91cb12c53e0c94b8aee87b06b44577348ba36512b
failed-tests-linux-musl-meson
96.6 KB
sha256:d90a43d851f55a59ad4448cb82f067eb4fd11f321db015f037976186798a475a
failed-tests-linux-reftable
99.5 KB
sha256:e3191d515ef0f355b706217e753dec65af10407c309bc3c8913716b23c8595ec
failed-tests-linux-reftable-leaks
100 KB
sha256:af154b7a20496c86d3c5be1658d3a2cba679222c824ba69cfc367d138f10a84f
failed-tests-linux-sha256
99.3 KB
sha256:44035a601c8f1d9f8a305f1eed1b4671858867fe565a9cac453b34422517474a
failed-tests-linux32
96.7 KB
sha256:e302cb4f7b69ed98b34eb2bd610e7061bb0d181365bb4b48e35c257d4937bdc8
windows-artifacts
96.7 MB
sha256:6ac840e8375cb0a5a5fcc2ca14300d63e6b8ec2abb61d8b875ea705608846a37
windows-meson-artifacts
57.2 MB
sha256:113962ebdbbfbc4ae2973ba70b5f8781db85b8558daf25dee036a52ae4391359