Fwd: trunk test failure in wininet/ftp.ok

[Dan Kegel]

Another example of why we shouldn't have the entire public
internet in the test harness.  Maybe this will get better once
we move the slaves to winehq, or maybe we'll need to add mocks
for all services we use, or maybe we can just punt and increase timeouts...

../../../tools/runtest -q -P wine -M wininet.dll -T ../../.. -p
wininet_test.exe.so ftp.c && touch ftp.ok
ftp.c:81: Test failed: Expected ERROR_INTERNET_LOGIN_FAILURE, got 12002

12002 is ERROR_INTERNET_TIMEOUT


---------- Forwarded message ----------
From:  <buildbot at kegel.com>
Date: Tue, Oct 4, 2011 at 4:29 AM
Subject: Re: trunk build
To: dank at kegel.com, wine-tests-results at winehq.org


This is an experimental automated build and test service.
Please feel free to ignore this email while we work the kinks out.

For more info about this message, see http://wiki.winehq.org/BuildBot

The Buildbot has detected a failed build on builder runtests-ati while
building Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests-ati/builds/42 (though
maybe not for long, as I'm still reinstalling the buildbot
periodically while experimenting)
BUILD FAILED: failed shell_3

Errors:
* Call to xpconnect wrapped JSObject produced this error:  *
* Call to xpconnect wrapped JSObject produced this error:  *
alarum: failed command was ../../../wine wininet_test.exe.so ftp.c
ftp.c:81: Test failed: Expected ERROR_INTERNET_LOGIN_FAILURE, got 12002
make: *** [ftp.ok] Error 1