On Sun, Jun 06, 2021 at 03:06:31PM -0400, Randall S. Becker wrote: > Just something to note: I was running git gc --aggressive on OpenSSL > today and got the same error as in this case. I'm assuming that the > fix will apply to that too. In this situation, the gc ran for over 2 > hours until failing. This may be a more widely available test > condition for fsync() EINTR, possibly. Thanks. One of my original questions was that we'd expect to see this in the wild, and not just the test suite. But it sounds like now we have. :) So I feel better that we have a full understanding of the issue. -Peff
