On February 16, 2019 13:06, Junio C Hamano wrote: > "Randall S. Becker" <rsbec...@nexbridge.com> writes: > > On February 16, 2019 3:27, Max Kirillov wrote: > >> What you could try is > >> https://public-inbox.org/git/20181124093719.10705-1- > m...@max630.net/ > >> (I'm not sure it would not conflict by now), this would remove > >> dependency between tests. If it helps it would be very valuable > information. > > > > Good news. This patch does seem to do the trick. I wonder whether this > > fixes the Azure build also. > > > > I have run the test under the following conditions: > > Run 1 (system idle): Pass > > Run 2 (system idle): Pass > > Run 3 (system idle): Pass > > Run 4 (system idle): Pass > > Run 5 (system idle): Pass > > Run 6 (system mild load, heavy file system): Pass Run 7 (system mild > > load, moderate file system load - git fetch): Pass Run 8 (heavy system > > load, heavy file system load): Pass Run 9 (--verbose, heavy system > > load, heavy file system load): Pass Run 10 (GIT_TRACE=true, --verbose, > > heavy system load, heavy file system > > load): Pass > > Run 11 (very heavy system load, very heavy file system load): Pass > > That indeed is a good news. > > > The current condition of the code is (the generate_zero_bytes delete > > was previously removed so can be ignored for the patch): > > Just to make sure I do not misunderstand, this result is with Max's patch but > without the generate_zero_bytes stuff?
Correct. > Thanks, all. Hopefully we can get this test failures behind us before -rc2; > knock, knock... Once the fix is integrated and in the usual spots, I can verify with haste. The full test cycle is now at 50 hours (argh), which I will rerun in full at rc2, but this one is fast.
