summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.main_config-glob
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2021-06-04 10:36:11 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-06-05 22:13:40 +0900
commitcccdfd22436ede80b37311e73a5c8339054a7ff1 (patch)
tree1de394e2112a271deebf6413fdbbe44f524bd2c5 /t/t5515/fetch.main_config-glob
parentGit 2.31.1 (diff)
downloadtgif-cccdfd22436ede80b37311e73a5c8339054a7ff1.tar.xz
fsync(): be prepared to see EINTR
Some platforms, like NonStop do not automatically restart fsync() when interrupted by a signal, even when that signal is setup with SA_RESTART. This can lead to test breakage, e.g., where "--progress" is used, thus SIGALRM is sent often, and can interrupt an fsync() syscall. Make sure we deal with such a case by retrying the syscall ourselves. Luckily, we call fsync() fron a single wrapper, fsync_or_die(), so the fix is fairly isolated. Reported-by: Randall S. Becker <randall.becker@nexbridge.ca> Helped-by: Jeff King <peff@peff.net> Helped-by: Taylor Blau <me@ttaylorr.com> [jc: the above two did most of the work---I just tied the loose end] Helped-by: René Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.main_config-glob')
0 files changed, 0 insertions, 0 deletions