Skip to content

t3454: cover merge-replay scenarios with the historian helper #2192

t3454: cover merge-replay scenarios with the historian helper

t3454: cover merge-replay scenarios with the historian helper #2192

Triggered via push May 6, 2026 00:36
Status Failure
Total duration 29m 18s
Artifacts 3

main.yml

on: push
win+VS build
0s
win+VS build
win+Meson build
1m 8s
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

63 errors, 42 warnings, and 12 notices
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
linux-musl-meson (alpine:latest): build/meson-private/tmpivsfcz_r/testfile.c#L6
/__w/git/git/build/meson-private/tmpivsfcz_r/testfile.c:6:17: 'arc4random_buf' undeclared (first use in this function)
linux-musl-meson (alpine:latest): build/meson-private/tmp37tos_rx/testfile.c#L4
/__w/git/git/build/meson-private/tmp37tos_rx/testfile.c:4:12: #error "Header 'sys/sysctl.h' could not be found"
linux-musl-meson (alpine:latest): build/meson-private/tmpqmcefc6z/testfile.c#L4
/__w/git/git/build/meson-private/tmpqmcefc6z/testfile.c:4:25: 'struct stat' has no member named 'st_mtimespec'
osx-meson (macos-14)
Process completed with exit code 1.
win+Meson build
Process completed with exit code 1.
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): kwset.c#L556
kwset.c:556:12: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-sha256 (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-meson (ubuntu:rolling)
Process completed with exit code 1.
linux-meson (ubuntu:rolling): build/meson-private/tmpj779vkps/testfile.c#L4
/__w/git/git/build/meson-private/tmpj779vkps/testfile.c:4:12: #error "Header 'sys/sysctl.h' could not be found"
linux-meson (ubuntu:rolling): build/meson-private/tmpsaxd0n2o/testfile.c#L4
/__w/git/git/build/meson-private/tmpsaxd0n2o/testfile.c:4:25: 'struct stat' has no member named 'st_mtimespec'
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./refs.h#L537
./refs.h:537:9: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-reftable (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
fedora-breaking-changes-meson (fedora:latest): build/meson-private/tmpkpdmarak/testfile.c#L4
/__w/git/git/build/meson-private/tmpkpdmarak/testfile.c:4:12: #error "Header 'sys/sysctl.h' could not be found"
fedora-breaking-changes-meson (fedora:latest): build/meson-private/tmpd3yprgnw/testfile.c#L4
/__w/git/git/build/meson-private/tmpd3yprgnw/testfile.c:4:25: 'struct stat' has no member named 'st_mtimespec'
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./refs.h#L537
./refs.h:537:9: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ident.c#L139
ident.c:139:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ident.c#L112
ident.c:112:33: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L945
./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
linux-asan-ubsan (ubuntu:rolling): ./git-compat-util.h#L344
./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]
documentation
Process completed with exit code 1.
linux-leaks (ubuntu:rolling)
failed: t3650.17 using replay on bare repo to perform basic cherry-pick
linux-leaks (ubuntu:rolling)
failed: t3650.16 using replay to perform basic cherry-pick
linux-leaks (ubuntu:rolling)
failed: t3650.15 using replay on bare repo to rebase with a conflict
linux-leaks (ubuntu:rolling)
failed: t3650.14 using replay to rebase with a conflict
linux-leaks (ubuntu:rolling)
failed: t3650.13 using replay on bare repo to rebase two branches, one on top of other
linux-leaks (ubuntu:rolling)
failed: t3650.12 using replay to rebase two branches, one on top of other
linux-leaks (ubuntu:rolling)
failed: t3650.11 reverting a merge commit is rejected
linux-leaks (ubuntu:rolling)
failed: t3650.10 replaying an octopus merge is rejected
linux-leaks (ubuntu:rolling)
failed: t3650.9 using replay to rebase a 2-parent merge
linux-leaks (ubuntu:rolling)
failed: t3454.6 preserves manual rename of pre-existing caller; does not extrapolate to new files
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.17 using replay on bare repo to perform basic cherry-pick
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.16 using replay to perform basic cherry-pick
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.15 using replay on bare repo to rebase with a conflict
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.14 using replay to rebase with a conflict
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.13 using replay on bare repo to rebase two branches, one on top of other
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.12 using replay to rebase two branches, one on top of other
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.11 reverting a merge commit is rejected
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.10 replaying an octopus merge is rejected
linux-reftable-leaks (ubuntu:rolling)
failed: t3650.9 using replay to rebase a 2-parent merge
linux-reftable-leaks (ubuntu:rolling)
failed: t3454.6 preserves manual rename of pre-existing caller; does not extrapolate to new files
linux-musl-meson (alpine:latest): build/meson-private/tmpeoe2dv_5/testfile.c#L10
/__w/git/git/build/meson-private/tmpeoe2dv_5/testfile.c:10:14: conflicting types for built-in function 'strdup'; expected 'char *(const char *)' [-Wbuiltin-declaration-mismatch]
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
osx-meson (macos-14)
JGit wasn't installed, see above for clues why
osx-meson (macos-14)
pcre2 10.47_1 is already installed and up-to-date. To reinstall 10.47_1, run: brew reinstall pcre2
osx-meson (macos-14)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
osx-meson (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
linux-meson (ubuntu:rolling): build/meson-private/tmpjrsco34k/testfile.c#L10
/__w/git/git/build/meson-private/tmpjrsco34k/testfile.c:10:14: conflicting types for built-in function 'strdup'; expected 'char *(const char *)' [-Wbuiltin-declaration-mismatch]
fedora-breaking-changes-meson (fedora:latest): build/meson-private/tmpbm1wpwr2/testfile.c#L10
/__w/git/git/build/meson-private/tmpbm1wpwr2/testfile.c:10:14: conflicting types for built-in function 'strdup'; expected 'char *(const char *)' [-Wbuiltin-declaration-mismatch]
fedora-breaking-changes-meson (fedora:latest)
JGit wasn't installed, see above for clues why
fedora-breaking-changes-meson (fedora:latest)
git-lfs wasn't installed, see above for clues why
fedora-breaking-changes-meson (fedora:latest)
perforce wasn't installed, see above for clues why
win 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/
debian-11 (debian:11)
JGit wasn't installed, see above for clues why
debian-11 (debian:11)
git-lfs wasn't installed, see above for clues why
debian-11 (debian:11)
perforce wasn't installed, see above for clues why
win test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
win test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
win test (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/
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
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 (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 (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
win test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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/
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/
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
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
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/
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-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
linux-reftable-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
win+Meson build
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win build
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (8)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (6)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (1)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (2)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (4)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (3)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (5)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (7)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
win test (9)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
failed-tests-linux-leaks
78.5 KB
sha256:66bc3499ccb3edd569c4f2b6d68debc29758165f67f3141ad7ce46bc2d0c82a7
failed-tests-linux-reftable-leaks
81.8 KB
sha256:2a19d22e47c3ecb11d76b08b4826cd62e1617611e49459013bf78c171b35e8ea
windows-artifacts
96.9 MB
sha256:795506c64ca727b8de5f191101502c8c6c74dd83c14bcdefdf30de488073be7c