Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integer expressions of different signedness: 'int' and 'size_t' {aka 'long unsigned int'} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:35: comparison of integer expressions of different signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Werror=sign-compare]

Process completed with exit code 1.

../builtin/push.c:679:35: comparison of integer expressions of different signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integer expressions of different signedness: 'int' and 'size_t' {aka 'long unsigned int'} [-Werror=sign-compare]

Process completed with exit code 1.

../builtin/push.c:679:35: comparison of integer expressions of different signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:35: comparison of integer expressions of different signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integer expressions of different signedness: 'int' and 'size_t' {aka 'long unsigned int'} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integer expressions of different signedness: 'int' and 'size_t' {aka 'unsigned int'} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long') [-Werror,-Wsign-compare]

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long') [-Werror,-Wsign-compare]

Process completed with exit code 1.

builtin/push.c:679:35: comparison of integer expressions of different signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Werror=sign-compare]

Process completed with exit code 1.

builtin/push.c:679:21: comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long') [-Werror,-Wsign-compare]

Process completed with exit code 1.

builtin/push.c:679:35: comparison of integer expressions of different signedness: 'int' and 'size_t' {aka 'long long unsigned int'} [-Werror=sign-compare]

Process completed with exit code 2.

Process completed with exit code 1.

Process completed with exit code 1.

failed: t5547.5 push to repo path with path separator (colon)

failed: t5547.2 accepted objects work

failed: t5517.13 push to mirrored repository with refspec fails

Process completed with exit code 1.

failed: t5538.6 push from full to shallow

failed: t5538.5 push from shallow to shallow

failed: t5538.4 add new shallow root with receive.updateshallow on

failed: t5538.3 push from shallow clone, with grafted roots

failed: t5538.2 push from shallow clone

failed: t5528.16 "matching" fails if none match

failed: t2027.5 ambiguous tracking info

failed: t5516.15 push without wildcard

failed: t5516.14 push with negotiation does not attempt to fetch submodules

failed: t5516.13 push deletion with negotiation

failed: t5516.12 push with negotiation proceeds anyway even if negotiation fails

failed: t5516.11 push with negotiation

failed: t5516.10 push without negotiation

failed: t2402.22 "list" all worktrees from linked with a bare main

failed: t2402.21 "list" all worktrees --porcelain from bare main

failed: t2402.20 "list" all worktrees from bare main

failed: t2402.19 bare repo setup

Process completed with exit code 1.

failed: t5534.12 fail without key and heed user.signingkey ssh

failed: t5534.8 ssh signed push sends push certificate

failed: t5534.5 push --signed=1 is accepted

failed: t5534.4 push --signed fails with a receiver without push certificate support

failed: t5534.3 talking with a receiver without push certificate support

failed: t5534.2 unsigned push does not send push certificate

failed: t5405.3 forced push should succeed

failed: t1416.7 interleaving hook calls succeed

failed: t5529.6 detect empty remote with existing local ref

failed: t5519.8 bob works and pushes again

failed: t5519.7 alice works and pushes yet again

failed: t5519.6 bob works and pushes

failed: t5519.5 alice works and pushes again

failed: t5519.4 clean-up in case the previous failed

failed: t5519.3 bob fetches from alice, works and pushes

failed: t5519.2 alice works and pushes

failed: t5519.1 setup

failed: t5400.17 receive-pack de-dupes .have lines

failed: t5813.17 fetch host:path (enabled)

failed: t5813.12 push host:path (enabled)

failed: t5813.11 fetch host:path (enabled)

failed: t5813.5 push host:path (enabled)

failed: t5813.4 fetch host:path (enabled)

failed: t5813.2 setup repository to clone

failed: t5710.18 clone and fetch with --filter=auto

failed: t5582.10 push --prune with negative refspec apply to the destination

failed: t5582.9 push --prune with negative refspec

failed: t5501.2 pushing into a repository with the same alternate

failed: t5504.28 fetch.fsck.unterminatedHeader=warn triggers error

failed: t5504.27 receive.fsck.unterminatedHeader=warn triggers error

failed: t5504.26 fetch with fetch.fsck.missingEmail=warn

failed: t5504.25 push with receive.fsck.missingEmail=warn

failed: t5504.23 fetch with fetch.fsck.skipList

failed: t5504.22 push with receive.fsck.skipList

failed: t5504.9 push with transfer.fsckobjects

failed: t5504.8 push with receive.fsckobjects

failed: t5504.7 push with !receive.fsckobjects

failed: t5504.6 push without strict

failed: t5531.12 push succeeds if submodule commit disabling recursion from cmdline overriding config

failed: t5531.11 push succeeds if submodule commit not on remote using on-demand from cmdline overriding config

failed: t5531.10 push recurse-submodules last one wins on command line

failed: t5531.9 push recurse-submodules on command line overrides config

failed: t5531.8 push succeeds if submodule commit not on remote but using auto-on-demand via submodule.recurse config

failed: t5531.7 push succeeds if submodule commit not on remote but using on-demand from config

failed: t5531.6 push succeeds if submodule commit not on remote but using on-demand on command line

failed: t5531.5 push succeeds after commit was pushed to remote

failed: t5531.3 push if submodule has no remote

failed: t5531.2 push works with recorded gitlink

failed: t5814.17 fetch remote-helper (enabled)

failed: t5814.12 push remote-helper (enabled)

failed: t5814.11 fetch remote-helper (enabled)

failed: t5814.5 push remote-helper (enabled)

failed: t5814.4 fetch remote-helper (enabled)

failed: t5814.2 setup repository to clone

failed: t5583.8 --all or --branches combines with --follow-tags have same behavior

failed: t5583.4 --all or --branches can not be combined with refspecs

failed: t5583.3 --all and --branches have the same behavior

failed: t5583.1 setup bare remote

Process completed with exit code 1.

failed: t5606.21 guesses initial branch name correctly

failed: t5401.13 pre-receive hook that forgets to read its input

failed: t0035.12 no trace in $GIT_DIR of a submodule

failed: t0035.1 setup an embedded bare repo, secondary worktree and submodule

JGit wasn't installed, see above for clues why

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

JGit wasn't installed, see above for clues why

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

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

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

JGit wasn't installed, see above for clues why

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

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

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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

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: git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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