March 2014 - Wine-Devel - list.winehq.org

Re: rpcrt4/tests: Add a couple of tests for marshalling an array of strings.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5719 Your paranoid android. === w2000pro (32 bit server) === server.c:1241: Test failed: expected Hello, got H# server.c:1243: Test failed: expected World!, got W# server.c:1253: Test failed: expected Hello, got L"H#\0178#\4d4c\4d45\86b8#\8640#" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H# server.c:1243: Test failed: expected World!, got W# server.c:1253: Test failed: expected Hello, got L"H#\0178#\4d4c\4d45\6868#\67c0#" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H# server.c:1243: Test failed: expected World!, got W# server.c:1253: Test failed: expected Hello, got L"H#\0198#\4d4c\4d45\7280#\6288#\7280#\0003\0004\0100\000c" server.c:1255: Test failed: expected World!, got L"W" === wxppro (32 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W$ server.c:1253: Test failed: expected Hello, got L"H$\01b8$\4d4c\4d45\0008" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H$ server.c:1243: Test failed: expected World!, got W$ server.c:1253: Test failed: expected Hello, got L"H$\0178$\4d4c\4d45\0008" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H$ server.c:1243: Test failed: expected World!, got W$ server.c:1253: Test failed: expected Hello, got L"H$\0408$\4d4c\4d45\0008" server.c:1255: Test failed: expected World!, got L"W" === wvista (32 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" === wvistau64 (32 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"Hdow\4d4c\4d45\0008" server.c:1255: Test failed: expected World!, got L"Wem3\4d4c\4d45\0008" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"Hem3\4d4c\4d45\0008" server.c:1255: Test failed: expected World!, got L"W;C:\4d4c\4d45\0008" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"Hdow\4d4c\4d45\0008" server.c:1255: Test failed: expected World!, got L"Wem3\4d4c\4d45\0008" === w2008s64 (32 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" === w7pro64 (32 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" === w8 (32 bit server) === server.c:984: Test failed: get_ranged_enum() returned 1997012995 instead of RE3 server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:984: Test failed: get_ranged_enum() returned -65533 instead of RE3 server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:984: Test failed: get_ranged_enum() returned 1997012995 instead of RE3 server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" === wvistau64 (64 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" === w2008s64 (64 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" === w7pro64 (64 bit server) === server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W" server.c:1241: Test failed: expected Hello, got H server.c:1243: Test failed: expected World!, got W server.c:1253: Test failed: expected Hello, got L"H" server.c:1255: Test failed: expected World!, got L"W"

March 17, 2014

Re: [PATCH 1/2] ddraw/tests: Add mipmap private data tests (try 2).

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5717 Your paranoid android. === w8 (32 bit ddraw4) === Failure running script in VM: timed out waiting for the child process

March 16, 2014

Re: [PATCH 2/2] ddraw/tests: Use a custom GUID for the private data tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5718 Your paranoid android. === build (build) === Patch failed to apply

March 16, 2014

Re: [PATCH 4/5] ddraw/tests: Use a custom GUID for the private data tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5715 Your paranoid android. === wvistau64 (64 bit ddraw7) === ddraw7.c:6044: Test failed: Failed to create surface, hr 0x80004002. === w2008s64 (64 bit ddraw7) === ddraw7.c:6044: Test failed: Failed to create surface, hr 0x80004002. === w7pro64 (64 bit ddraw7) === ddraw7.c:6044: Test failed: Failed to create surface, hr 0x80004002. === w8 (32 bit ddraw4) === No test summary line found Failure running script in VM: network read timed out (wait2:ListSize:0/4)

March 16, 2014

Re: [PATCH 3/5] ddraw/tests: Add mipmap private data tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5714 Your paranoid android. === w8 (32 bit ddraw7) === Failure running script in VM: timed out waiting for the child process === wvistau64 (64 bit ddraw7) === ddraw7.c:6030: Test failed: Failed to create surface, hr 0x80004002. === w2008s64 (64 bit ddraw7) === ddraw7.c:6030: Test failed: Failed to create surface, hr 0x80004002. === w7pro64 (64 bit ddraw7) === ddraw7.c:6030: Test failed: Failed to create surface, hr 0x80004002. === w8 (32 bit ddraw4) === ddraw4.c:5731: Test failed: Got unexpected refcount 3. ddraw4.c:5750: Test failed: Got unexpected refcount 3. ddraw4.c:5757: Test failed: Got unexpected hr 0. ddraw4.c:5760: Test failed: Got unexpected refcount 3. ddraw4.c:5762: Test failed: Got unexpected refcount 2. ddraw4.c:5768: Test failed: Got unexpected hr 0. ddraw4.c:5771: Test failed: Got unexpected refcount 2. ddraw4.c:5773: Test failed: Got unexpected refcount 1. ddraw4.c:5775: Test failed: Got unexpected refcount 6.

March 16, 2014

Re: [PATCH 2/5] ddraw/tests: Test GetPrivateData size behavior.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5713 Your paranoid android. === w8 (32 bit ddraw7) === ddraw7.c:5604: Test failed: Got unexpected refcount 3. ddraw7.c:5623: Test failed: Got unexpected refcount 3. ddraw7.c:5630: Test failed: Got unexpected hr 0. ddraw7.c:5633: Test failed: Got unexpected refcount 3. ddraw7.c:5635: Test failed: Got unexpected refcount 2. ddraw7.c:5641: Test failed: Got unexpected hr 0. ddraw7.c:5644: Test failed: Got unexpected refcount 2. ddraw7.c:5646: Test failed: Got unexpected refcount 1. ddraw7.c:5648: Test failed: Got unexpected refcount 6. ddraw7.c:5765: Test failed: Failed to set cooperative level, hr 0x8876023b. === w8 (32 bit ddraw4) === The test timed out

March 16, 2014

Re: gdi32/tests: Mark Win8.1 behaviour for johab charset as broken

by Akihiro Sagawa

On Sat, 15 Mar 2014 00:15:54 +0100, André Hentschel wrote: > - {JOHAB_CHARSET, 0x8446, 0x3135, > + {JOHAB_CHARSET, 0x8446, 0x3135, TRUE /* Win8.1 */, > {TRUE, TRUE, FALSE, FALSE, TRUE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, TRUE}}, (snip) > + ok((pGetCharABCWidthsA(hdc, c[i].a, c[i].a + 1, a) && > + pGetCharABCWidthsW(hdc, c[i].w, c[i].w + 1, w) && > + memcmp(a, w, sizeof a) == 0) || broken(c[i].broken), > "GetCharABCWidthsA and GetCharABCWidthsW should return same widths. charset = %u\n", c[i].cs); Regarding this test about Johab charset, you are missing the point. Which version of Windows does succeed in? I suspect that the test is broken. Don't you think? As far as I know, other wine testbots just skip the test due to missing Johab (=130) charset font. Moreover, my Windows 7 with Arial Unicode MS or YOzFont[1] doesn't pass because GetCharABCWidthsA returns 0. But I've not tested on Korean version Windows. If you have further information, please let me know. [1] YOzFont apparently supports Johab charset. It's available from http://yozvox.web.fc2.com/446F776E6C6F6164.html Regards, Akihiro Sagawa

March 16, 2014

Re: cmd: Dont assume cmd.exe is the first argument

by Qian Hong

Hi Alistair, + args = 0; /* start at first arg, skipping cmd.exe itself */ Could you also consider fixing the comment here? Have a nice weekend :) -- Regards, Qian Hong - http://www.winehq.org

March 16, 2014

Re: About GSoC - The Wine Project

by Stefan Dösinger

Am 15.03.2014 um 19:27 schrieb SpedsT . <spedst(a)yahoo.com>: > Hello. I want to apply to this project and I have a question about this note: > • Note: Beginning with Summer of Code 2014, applicants *MUST* have submitted a patch or testcase to wine-patches (see http://wiki.winehq.org/SubmittingPatches) to be considered for acceptance. > What kind of patch or testcase should I submit, what would you like to be about? Ideally one that is related to your gsoc application. E.g. if you want to work on the command parser, send some tests for the command parser. Cheers, Stefan

March 15, 2014

FYI Re: wined3d_mutex

by Max TenEyck Woodbury

I have told you about the long delays I have encountered with Guild Wars 2 under wine. I mentioned that I suspected the wined3d_mutex was the source of the problem. I have just finished a test that shows that it is NOT the source of this problem. Specifically, I dummied the wined3d_mutex_lock and wined3d_mutex_unloc procedures so that they did nothing, That version showed the same pattern of delays that the unaltered system showed. If anybody has an idea about what might be causing these delays, please tell me. Note that my review of the use of this mutex indicates that it is of very questionable value. In my opinion it should be replaced by a set of read/write locks built into the individual data structures. Comments? max

March 15, 2014