You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge pull request git-for-windows#378: Scalar: Fix some flaky tests with retry logic and better GVFS Protocol awareness
I ran the Scalar functional tests at least 10 times before getting a full green build. One of the most common failures was a failure during `scalar clone` with a strange error. Looking at the TRACE2 logs, I found these entries:
```
d0 | main | child_start | | 0.159207 | | | [ch2] class:? argv:[git fetch --quiet origin]
d0 | main | child_exit | | 15.823433 | 15.664226 | | [ch2] pid:16571 code:128
d0 | main | error | | | | | Partial clone failed; Trying full clone
d0 | main | error | | | | | could not configure for full clone
d0 | main | exit | | 15.823775 | | | code:1
d0 | main | atexit | | 15.823790 | | | code:1
```
This means that the first `git fetch` failed for some reason, and we started running `set_config()` to un-set the partial-clone config options. However, we are not in a partial clone at this state! We are working against Azure Repos.
There are two things in this PR that should help:
1. Add retry logic to `run_git()` which will retry the `git fetch` when it fails (also other subcommands).
2. Fix this use of `set_config()` by skipping it if we are using the GVFS Protocol.
0 commit comments