On Tue, Oct 28, 2008 at 1:37 AM, Hans Leidekker hans@codeweavers.com wrote:
... I guess we could increase sleep between two tests that query the same host once more, or just pick another host.
Any test that uses the public internet is buggy and is bound to fail often enough to annoy people when run as part of an automated test system; that's http://bugs.winehq.org/show_bug.cgi?id=15716 I suspect that's what's happening here.
Since only automated test systems run these tests, we could have an optional shell script, run manually on systems that have to run the tests really reliably, that sets up a local server and adds entries to /etc/hosts. Or we could implement our own mock servers as part of the tests in question.
Hans, since it's your code that's failing here, can you think of anything we can do to make the test pass even if the public internet is going up and down like a bounce house? Skipping the test if the first use of the internet fails isn't good enough, since the internet might go up and down during the test several times. - Dan