October 2012 - Wine-devel - list.winehq.org

Re: msvcp90: fix parsing in num_get<>::_Getifld
by Piotr Caban 11 Oct '12

11 Oct '12

On 10/11/12 00:27, Daniel Lehman wrote: - if(!base && first->strbuf && first->val==digits[0]) { + if(first->strbuf && first->val==digits[0]) { + found_zero = TRUE; istreambuf_iterator_wchar_inc(first); if(first->strbuf && (first->val==mb_to_wc('x', &this->cvt) || first->val==mb_to_wc('x', &this->cvt))) { There's a comparision to 'x' 2 times, one of them should be 'X'. Cheers, Piotr

1 0

Re: [PATCH 17/25] winmm/tests: Add initial set of MCI MIDI tests (incl. DeleteFile)
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22026 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

2 1

Re: [PATCH 4/4] mshtml: Added IHTMLDocument::get_charset implementation
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22114 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [1/2] dinput/tests: Test for DIPROP_INSTANCENAME and DIPROP_GUIDANDPATH
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22112 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Re: wined3d: recognize Radeon HD 6670
by Henri Verbeet 11 Oct '12

11 Oct '12

On 5 October 2012 22:12, Austin English <austinenglish(a)gmail.com> wrote: > Fixes http://bugs.winehq.org/show_bug.cgi?id=31891 > That doesn't look right (and doesn't do what you think it does anyway), did you verify this against the Windows driver? It probably just needs an entry to map "HD 6670" to CARD_AMD_RADEON_HD6600, although it's a bit curious that most of the existing entries for NI have generic strings like "HD 6600".

2 1

Re: shell32: Standardize on the ShellExecuteEx() terminology.
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22104 Your paranoid android. === WNT4WSSP6 (32 bit shlexec) === shlexec.c:1420: Test failed: ShellExecuteEx(mask="0x200", verb="Params23456", file="C:\TEMP\wt1.tmp\test file.shlexec", params="p2 "p3" "p4 is lost"): the cmdline is ' "p2" "p3" "p3" "" ""' instead of ' "p2" "p3" "" "" ""' === W2KPROSP4 (32 bit shlexec) === shlexec.c:1420: Test failed: ShellExecuteEx(mask="0x200", verb="Params23456", file="C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.shlexec", params="p2 "p3" "p4 is lost"): the cmdline is ' "p2" "p3" "p3" "" ""' instead of ' "p2" "p3" "" "" ""'

1 0

Re: shell32/tests: Test ShellExecute()'s URL handling.
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22103 Your paranoid android. === WNT4WSSP6 (32 bit shlexec) === shlexec.c:1438: Test failed: ShellExecuteEx(mask="0x200", verb="Params23456", file="C:\TEMP\wt1.tmp\test file.shlexec", params="p2 "p3" "p4 is lost"): the cmdline is ' "p2" "p3" "p3" "" ""' instead of ' "p2" "p3" "" "" ""' shlexec.c:1790: Test failed: ShellExecute(file="notaproto://foo") succeeded: rc=2 shlexec.c:1793: Test failed: ShellExecute(file="fakeproto://foo/bar") expected SE_ERR_ACCESSDENIED got rc=2 shlexec.c:152: Test failed: ShellExecute(file="shlproto://foo/bar") Got different return value with empty string: 42 2 shlexec.c:152: Test failed: ShellExecute(file="shlproto://foo/bar.lnk") Got different return value with empty string: 42 2 shlexec.c:1822: Test failed: argvA4 expected 'shlproto://C:\TEMP\wt1.tmp/bar', got 'shlproto://%TMPDIR%/bar' shlexec.c:137: Test failed: ShellExecute(file="file://shlproto://foo/bar") WaitForSingleObject returned 258 shlexec.c:152: Test failed: ShellExecute(file="file://shlproto://foo/bar") Got different return value with empty string: 42 2 shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=42 === W2KPROSP4 (32 bit shlexec) === shlexec.c:1438: Test failed: ShellExecuteEx(mask="0x200", verb="Params23456", file="C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.shlexec", params="p2 "p3" "p4 is lost"): the cmdline is ' "p2" "p3" "p3" "" ""' instead of ' "p2" "p3" "" "" ""' shlexec.c:1822: Test failed: argvA4 expected 'shlproto://C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp/bar', got 'shlproto://%TMPDIR%/bar' shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=5 === WVISTAADM (32 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2 === W2K8SE (32 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2 === W7PRO (32 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2 === W7PROX64 (32 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2 === TEST64_W7SP1 (32 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2 === W7PROX64 (64 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2 === TEST64_W7SP1 (64 bit shlexec) === shlexec.c:1833: Test failed: ShellExecute(file="file://shlproto://foo/bar") succeeded: rc=2

1 0

Re: vbscript: Fixed tests on some non-English configs (without '.' as decimal point)
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22091 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

1 0

Re: [PATCH] vbscript: Undefined variables resolve as EMPTY without Option Explicit
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22090 Your paranoid android. === W2KPROSP4 (32 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5" === WXPPROSP3 (32 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5" === W2K3R2SESP2 (32 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5" === W7PROX64 (32 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5" === TEST64_W7SP1 (32 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5" === W7PROX64 (64 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5" === TEST64_W7SP1 (64 bit run) === run.c:939: Test failed: api.vbs: L"CStr(3,5) = 3,5"

1 0

Re: shell32: Fix ShellExecute()'s handling of file URLs.
by Marvin 11 Oct '12

11 Oct '12

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 http://testbot.winehq.org/JobDetails.pl?Key=22079 Your paranoid android. === WNT4WSSP6 (32 bit shlexec) === shlexec.c:1440: Test failed: ShellExecuteEx(mask="0x200", verb="Params23456", file="C:\TEMP\wt1.tmp\test file.shlexec", params="p2 "p3" "p4 is lost"): the cmdline is ' "p2" "p3" "p3" "" ""' instead of ' "p2" "p3" "" "" ""' === W2KPROSP4 (32 bit shlexec) === shlexec.c:1440: Test failed: ShellExecuteEx(mask="0x200", verb="Params23456", file="C:\DOCUME~1\winetest\LOCALS~1\Temp\wt1.tmp\test file.shlexec", params="p2 "p3" "p4 is lost"): the cmdline is ' "p2" "p3" "p3" "" ""' instead of ' "p2" "p3" "" "" ""'

1 0