| commit | 72d63b2f45e46ab7dbcd0102f3922fd02f5e1573 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Tue, 29 Jan 2019 14:19:31 +0000 (29 06:19 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 29 Jan 2019 17:26:46 +0000 (29 09:26 -0800) | ||
| tree | 858f6d8ea06879cb9f56015b09a6f5a5f8735fea | treesnapshot (tar.gz zip) |
| parent | 6c1f4ae65ad62f33c85884c723aa2c8a57207b85 | commitdiff |
mingw: be more generous when wrapping up the setitimer() emulation
Every once in a while, the Azure Pipeline fails with some semi-random
error: timer thread did not terminate timely
This error message means that the thread that is used to emulate the
setitimer() function did not terminate within 1,000 milliseconds.
The most likely explanation (and therefore the one we should assume to
be true, according to Occam's Razor) is that the timeout of one second
is simply not enough because we try to run so many tasks in parallel.
So let's give it ten seconds instead of only one. That should be enough.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Every once in a while, the Azure Pipeline fails with some semi-random
error: timer thread did not terminate timely
This error message means that the thread that is used to emulate the
setitimer() function did not terminate within 1,000 milliseconds.
The most likely explanation (and therefore the one we should assume to
be true, according to Occam's Razor) is that the timeout of one second
is simply not enough because we try to run so many tasks in parallel.
So let's give it ten seconds instead of only one. That should be enough.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| compat/mingw.c | diffblobblamehistory |