From: Stefan Sperling Subject: Re: got-build-regress.sh regress failure To: gameoftrees@openbsd.org Date: Fri, 27 Dec 2024 10:34:11 +0100 On Fri, Dec 27, 2024 at 03:14:38AM +0100, stsp@stsp.name wrote: > got-build-regress.sh for branch 'main' on Fri Dec 27 01:30:09 UTC 2024 > > ==== clone ==== > ./clone.sh -q -r "/tmp" > error: RPC failed; curl 18 transfer closed with outstanding read data remaining > fatal: the remote end hung up unexpectedly > git clone command failed unexpectedly > test failed; leaving test data in /tmp/got-test-clone_basic_http-9gAVr244dy > *** Error 1 in regress/cmdline (Makefile:82 'clone') > FAILED > *** Error 1 in regress/cmdline (:105 'regress': if make -C /home/stsp/got/regress/cmdline clone; then echo -n "SUCCESS " | ...) > *** Error 2 in regress (:48 'all': @for entry in cmdline delta deltify idset path fetch tog secrets; do set -e; if test -d /...) > *** Error 2 in /home/stsp/got (:62 'regress': @set -e; if test -d /home/stsp/got/regress.arm64; then _newdir_=regress.arm64;...) > > > Test failures: > > test failed; leaving test data in /tmp/got-test-clone_basic_http-9gAVr244dy I could not yet figure out why this is happening. I've seen this test fail in a similar way twice, when I ran it manually. But when running it in a loop this test seems to keep passing. Trace of the other failures I've seen below. In both cases, http-server.log contains 'ready\n'. $ ./clone.sh test_clone_basic_http test_clone_basic_http fatal: unable to access 'http://127.0.0.1:8080/repo/': get sockname() failed with errno 22: Invalid argument git clone command failed unexpectedly test failed; leaving test data in /tmp/got-test-clone_basic_http-9q2vniwLJ6 $ ./clone.sh test_clone_basic_http test_clone_basic_http fatal: unable to access 'http://127.0.0.1:8080/repo/': Emp ty reply from server git clone command failed unexpectedly test failed; leaving test data in /tmp/got-test-clone_basic_http-2iGlFTR7Tx Seems like a problem with our perl-based http server, perhaps specific to arm64 machines? Any ideas?