Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Check both IPv4 and IPv6 ports explicitly
In each CI run with failing journey tests due to not being able to connect to `git daemon`, there are also passing tests, and in each run that I have observed, including an early run presented in GitoxideLabs#1634 (https://github.com/GitoxideLabs/gitoxide/actions/runs/12359365805/job/34491924319?pr=1634#step:6:1049), all passing journey tests (of those with non-skipped contents) that connect to the git daemon do so after `nc` has reported success connecting to `::1` (IPv6 loclahost), and the failing journey test that attempts to connect to the git daemon does so after `nc` has reported success connecting to `127.0.0.1` (IPv4 localhost). That doesn't clearly elucidate what would be going wrong, and it is possible that the problem is unrelaced, but it looks worthwhile to check into it. At this point, the git daemon is still not told what to listen on. First I just want to see what `nc` reports when checking for both to ensure that nothing is listening on either of them each time `git-daemon` is about to be run.
- Loading branch information