Am Mon, 2002-12-02 um 19.12 schrieb Francois Gouget:
Am Sam, 2002-11-30 um 04.02 schrieb Francois Gouget:
Come on people, we can do better. Send fixes to wine-patches, and send me emails to so that I update this table.
I'll have a look at the winsock stuff.
Thanks :-)
I am currently having trouble with running stuff natively on Windows. Can anybody run the winsock test with verbose output (trace enabled) on Windows NT and send me the result ?
Martin
On 2 Dec 2002, Martin Wilck wrote: [...]
I am currently having trouble with running stuff natively on Windows. Can anybody run the winsock test with verbose output (trace enabled) on Windows NT and send me the result ?
Here goes:
sock.c:686: **** STARTING TEST 0 **** sock.c:327:simple_server (b2) starting sock.c:386:simple_client (dd): starting sock.c:336:simple_server (b2) ready sock.c:389:simple_client (dd): server ready sock.c:341:simple_server (b2): waiting for client sock.c:386:simple_client (28): starting sock.c:389:simple_client (28): server ready sock.c:401:simple_client (dd) connected sock.c:341:simple_server (b2): waiting for client sock.c:422:simple_client (dd) exiting sock.c:401:simple_client (28) connected sock.c:369:simple_server (b2) exiting sock.c:422:simple_client (28) exiting sock.c:607: Test failed: some threads have not completed
sock.c:688: **** TEST 0 COMPLETE **** sock.c:686: **** STARTING TEST 1 **** sock.c:327:simple_server (a5) starting sock.c:336:simple_server (a5) ready sock.c:341:simple_server (a5): waiting for client sock.c:440:event_client (ce): starting sock.c:440:event_client (cc): starting sock.c:442:event_client (ce): server ready sock.c:451: Test failed: event_client (ce): connect error: 10022 sock.c:442:event_client (cc): server ready sock.c:451: Test failed: event_client (cc): connect error: 10022 sock.c:607: Test failed: some threads have not completed
sock.c:613:terminating thread 000000a5 sock.c:613:terminating thread 000000ce sock.c:613:terminating thread 000000cc sock.c:688: **** TEST 1 COMPLETE ****
There is no further output. The process does not terminate and has 1 remaining thread at this point.
Hi Francois,
You may have seen that Alexandre applied my patch, so the winsock test issue appears to be fixed.
I inserted an #ifdef _WIN32 clause at the top to adjust includes to run with VC++. I wonder if this should be done for all test programs to avoid the editing hassle.
The "Running tests on Windows" section in the Wine docs _definitely needs correction_. It currently doesn't talk about running tests on Windows at all - it covers running tests in Wine!! Besides, it is largely out of date, talking about perl tests and such.
With the current docs, my level of wine experience, and a fair amount of googling, it took me about 2 hours to find out how to get the tests running on Windows (1 - do "make test" in wine, 2 - copy .c files and wine/test.h to Windows, 3 - import everything into a VC++ project, 4 - adjust #include directives with trial and error, 5 - go for it).
I guess for newbies it will be pretty much impossible to figure this out. Or is there a really simple way that I just missed?
Martin
On December 4, 2002 04:35 am, Martin Wilck wrote:
I guess for newbies it will be pretty much impossible to figure this out. Or is there a really simple way that I just missed?
This is why I think we need someone to build the tests, and make them available for people to run on Windows. Even if we simplify the process (which we should do!), it's still too much trouble if we want to have them tests on many different Windows versions at regular intervals.
-
Dimitrie O. Paun -
Francois Gouget -
Martin Wilck