./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

Process completed with exit code 2.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 2.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./refs.h:537:9: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 2.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:945:6: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

./git-compat-util.h:344:11: '_Generic' is a C11 extension [-Werror,-Wc11-extensions]

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5514.10 git fetch --multiple (ignoring skipFetchAll)

failed: t5514.9 git fetch --all (skipFetchAll)

Process completed with exit code 1.

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

Process completed with exit code 1.

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5404.7 already deleted tracking branches ignored

Process completed with exit code 1.

failed: t5514.10 git fetch --multiple (ignoring skipFetchAll)

failed: t5514.9 git fetch --all (skipFetchAll)

failed: t5505.121 refs/remotes/* <src> refspec and unqualified <dst> DWIM and advice

failed: t5505.65 update (with remotes.default defined)

failed: t5505.64 update default (overridden, with funny whitespace)

failed: t5505.63 update default

failed: t5505.61 update with arguments

failed: t5505.37 set-head --auto has no problem w/multiple HEADs

failed: t5505.27 show -n

failed: t5505.25 show with negative refspecs

failed: t5505.24 show

failed: t5404.7 already deleted tracking branches ignored

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

git-lfs wasn't installed, see above for clues why

perforce wasn't installed, see above for clues why

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

git-lfs wasn't installed, see above for clues why

perforce wasn't installed, see above for clues why

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

git-lfs wasn't installed, see above for clues why

perforce wasn't installed, see above for clues why

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 16th, 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/

JGit wasn't installed, see above for clues why

git-lfs wasn't installed, see above for clues why

perforce wasn't installed, see above for clues why

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

git-lfs wasn't installed, see above for clues why

perforce wasn't installed, see above for clues why

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 16th, 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/

JGit wasn't installed, see above for clues why

Already linked: /opt/homebrew/Cellar/gettext/1.0

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 16th, 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/

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

pcre2 10.47_1 is already installed and up-to-date. To reinstall 10.47_1, run: brew reinstall pcre2

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

Already linked: /opt/homebrew/Cellar/gettext/1.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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

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 16th, 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/

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 16th, 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/

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 16th, 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/

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

Already linked: /opt/homebrew/Cellar/gettext/1.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 16th, 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/

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 16th, 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/

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 16th, 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/

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 16th, 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/

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 16th, 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/

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 16th, 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/

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 16th, 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/

JGit wasn't installed, see above for clues why

Already linked: /opt/homebrew/Cellar/gettext/1.0

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026