November 2013 - Wine-devel - list.winehq.org

Re: kernel32: use ANSI code page if current thread locale has no code page (try 4)
by Alexandre Julliard 07 Nov '13

07 Nov '13

Daniel Lehman <dlehman(a)esri.com> writes: > + for (i = 0; i < sizeof(lcids)/sizeof(lcids[0]); i++) > + { > + SetThreadLocale(lcids[i].lcid); > + > + GetLocaleInfoA(lcids[i].lcid, LOCALE_IDEFAULTANSICODEPAGE|LOCALE_RETURN_NUMBER, (LPSTR)&cp, sizeof(cp)); > + ok(cp == lcids[i].defacp, "wrong codepage %i for lcid %04x, should be %04x\n", cp, lcids[i].defacp, cp); > + > + /* GetCPInfoEx/GetCPInfo - CP_ACP */ > + memset(&cpi, 0, sizeof(cpi)); > + GetCPInfoExA(CP_ACP, 0, &cpi); > + ok(cpi.CodePage == 1252 /* ANSI Latin 1 */, "wrong codepage %i for lcid %04x, should be 1252\n", > + cpi.CodePage, lcids[i].lcid); This should be checked against the current locale, there's no reason that it would always be 1252. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: wininet: Check if connection is alive before sending request.
by Marvin 06 Nov '13

06 Nov '13

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=3250 Your paranoid android. === w2008s64 (64 bit http) === http.c:3520: Test failed: HttpQueryInfo failed 0 === w7pro64 (64 bit http) === http.c:3520: Test failed: HttpQueryInfo failed 0

1 0

Re: [1/2] msctf/tests: Always set focus again explicitly for Win7+
by Marvin 06 Nov '13

06 Nov '13

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=3245 Your paranoid android. === w864 (64 bit inputprocessor) === inputprocessor.c:791: Test failed: Deactivation came unexpectedly

1 0

Re: [PATCH 3/3] ws2_32: Add an interactive test for interface change notifications.
by Marvin 06 Nov '13

06 Nov '13

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=3242 Your paranoid android. === wxppro (32 bit sock) === sock.c:519: Test failed: oob_server (764): unexpectedly at the OOB mark: 0 === w2008s64 (32 bit sock) === sock.c:519: Test failed: oob_server (7a4): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 757C9799 === w7pro64 (32 bit sock) === sock.c:528: Test failed: oob_server (968): not at the OOB mark: 1 === w864 (32 bit sock) === sock.c:1740: Test failed: sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004 === w2008s64 (64 bit sock) === sock.c:519: Test failed: oob_server (744): unexpectedly at the OOB mark: 0 No test summary line found === w7pro64 (64 bit sock) === sock.c:528: Test failed: oob_server (968): not at the OOB mark: 1 === w864 (64 bit sock) === sock.c:1740: Test failed: sock.c:1740: Test failed: getservbyname could not retrieve information for telnet: 11004

1 0

Re: [PATCH 2/2] jscript: Improved error handling in numeric literal parser.
by Marvin 06 Nov '13

06 Nov '13

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=3231 Your paranoid android. === wxppro (32 bit) === No test summary line found === wvista (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7pro64 (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === w864 (32 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found === w7pro64 (64 bit) === No test summary line found === w864 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/2] jscript: Added support for octal literals.
by Marvin 06 Nov '13

06 Nov '13

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=3230 Your paranoid android. === wxppro (32 bit) === No test summary line found === wvista (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7pro64 (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === w864 (32 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found === w7pro64 (64 bit) === No test summary line found === w864 (64 bit) === No test summary line found

1 0

Re: [2/2] user32/tests: Use BOOL type where appropriate
by Marvin 05 Nov '13

05 Nov '13

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=3223 Your paranoid android. === w8 (32 bit msg) === msg.c:8363: Test failed: did not get expected count for minimum timeout (54 != ~64). === w8 (32 bit sysparams) === sysparams.c:2790: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2792: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784 sysparams.c:2488: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2501: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1 === w864 (32 bit sysparams) === sysparams.c:2790: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2792: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784 sysparams.c:2488: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2501: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1 === w864 (64 bit sysparams) === sysparams.c:2790: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2792: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784

1 0

Re: [1/2] user32/tests: Check return code from call to SystemParametersInfo
by Marvin 05 Nov '13

05 Nov '13

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=3222 Your paranoid android. === w8 (32 bit sysparams) === sysparams.c:2792: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2794: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784 sysparams.c:2490: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2503: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1 === w864 (32 bit sysparams) === sysparams.c:2792: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2794: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784 sysparams.c:2490: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out sysparams.c:2503: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1 === w864 (64 bit sysparams) === sysparams.c:2792: Test failed: GetSystemMetrics(SM_CXMAXTRACK): expected 1044 or 1036 actual 1040 sysparams.c:2794: Test failed: GetSystemMetrics(SM_CYMAXTRACK): expected 788 or 780 actual 784

1 0

Re: [2/2] ntdll: Enable compilation with -D__WINESRC__
by Marvin 05 Nov '13

05 Nov '13

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=3218 Your paranoid android. === w2008s64 (64 bit port) === port.c:186: Test failed: Expected STATUS_SUCCESS, got c0000005 Timeout === w7pro64 (64 bit port) === port.c:186: Test failed: Expected STATUS_SUCCESS, got c0000005 Timeout

1 0

Re: [PATCH] user32: fixed sizeof() to MultiByteToWideChar
by Marvin 05 Nov '13

05 Nov '13

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=3217 Your paranoid android. === w864 (32 bit class) === class.c:690: Test failed: Windows should be Unicode

1 0