I'm running into http://bugs.winehq.org/show_bug.cgi?id=15716 more and more often. We really need to set up mock servers so test cases don't need to rely on the public internet.
I'm slowly bringing up a second patchwatcher using the newly refactored code. I even wrote some documentation on how to set up a patchwatcher instance: http://code.google.com/p/winezeug/source/browse/trunk/patchwatcher/readme.tx... I don't really recommend anybody (but Rob) try to do this until we finish working out the bugs, though.
On Sunday 26 October 2008 23:00:51 Dan Kegel wrote:
I'm running into http://bugs.winehq.org/show_bug.cgi?id=15716 more and more often. We really need to set up mock servers so test cases don't need to rely on the public internet.
Samba has a socket wrapper library that fakes network access. It's not going to work on Wine the way Samba did it (I tried and failed), but I'd be interested in implementing something similar for Wine. Ideally, it'd be compatible to Samba so I can use it for testing, but there's no reason the internet tests can't use that as well.
The issue here is that we need to do some pre-setup on the environment we run in, ideally in a way that works on Windows as well. This seems to be hard, so I might be overengineering things. If you think something that for now only runs on Wine would be useful, I can give that a shot.
Cheers, Kai
Dan Kegel wrote:
I'm running into http://bugs.winehq.org/show_bug.cgi?id=15716 more and more often. We really need to set up mock servers so test cases don't need to rely on the public internet.
I'm slowly bringing up a second patchwatcher using the newly refactored code. I even wrote some documentation on how to set up a patchwatcher instance: http://code.google.com/p/winezeug/source/browse/trunk/patchwatcher/readme.tx... I don't really recommend anybody (but Rob) try to do this until we finish working out the bugs, though.
Dan:
+1, unless the test case specifically is to test Internet connectivity.
James McKenzie
Kai wrote:
Dan Kegel dank@kegel.com wrote:
I'm running into http://bugs.winehq.org/show_bug.cgi?id=15716 more and more often. We really need to set up mock servers so test cases don't need to rely on the public internet.
Samba has a socket wrapper library that fakes network access...
I was thinking of something cruder: an option that causes all hostname-to-IP-address resolution to resolve to 127.0.0.1, and then make that the default when running conformance tests. It would break lots of tests, so we would have to mark them todo_wine at the same time, or something.
From: "Dan Kegel" dank@kegel.com wrote:
I'm running into http://bugs.winehq.org/show_bug.cgi?id=15716 more and more often. We really need to set up mock servers so test cases don't need to rely on the public internet.
If a test fails due to missing internet access that's a bug in the test. The test should be skipped in such a case, and many tests already behave that way. Do you have a list of broken tests?
On Sun, Oct 26, 2008 at 8:56 PM, Dmitry Timoshkov dmitry@codeweavers.com wrote:
I'm running into http://bugs.winehq.org/show_bug.cgi?id=15716 more and more often. We really need to set up mock servers so test cases don't need to rely on the public internet.
If a test fails due to missing internet access that's a bug in the test. The test should be skipped in such a case, and many tests already behave that way. Do you have a list of broken tests?
No, but it will be easy to generate once we have an option to cause all name resolution to return 127.0.0.1.
-
Dan Kegel -
Dmitry Timoshkov -
James McKenzie -
Kai Blin