busy loops in tests 502, 555, and 573
Date: Fri, 26 Aug 2011 11:26:16 +0200
I spotted that tests 502, 555, and 573 do not call select() when looping
around curl_multi_perform(). Is that intentionally?
We have been observing random timout events on 555 and 573 when running
through valgrind on our overloaded virtualized Fedora build hosts. Adding
select() to those tests seems to solve (or at least suppress) the problem.
A tentative patch is attached.
- text/x-patch attachment: 0001-tests-break-busy-loops-in-tests-502-555-and-573.patch