May 2016 - Wine-Devel - list.winehq.org

Re: ddraw/tests: Fix a typo in an ok() call
by Marvin May 18, 2016

May 18, 2016

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://testbot.winehq.org/JobDetails.pl?Key=23075 Your paranoid android. === w864 (32 bit d3d) === d3d.c:2326: Test failed: Unexpected destination texture level pixels; 2031 differences at 0 level d3d.c:2326: Test failed: Unexpected destination texture level pixels; 518 differences at 1 level d3d.c:2326: Test failed: Unexpected destination texture level pixels; 138 differences at 2 level d3d.c:2326: Test failed: Unexpected destination texture level pixels; 46 differences at 3 level d3d.c:2510: Test failed: Unexpected destination texture level pixels; 257 differences d3d.c:2657: Test failed: Unexpected destination texture level pixels; 256 differences at 2 level d3d.c:2657: Test failed: Unexpected destination texture level pixels; 64 differences at 3 level d3d.c:2657: Test failed: Unexpected destination texture level pixels; 16 differences at 4 level d3d.c:2657: Test failed: Unexpected destination texture level pixels; 4 differences at 5 level === w1064 (32 bit d3d) === d3d.c:2326: Test failed: Unexpected destination texture level pixels; 2031 differences at 0 level d3d.c:2326: Test failed: Unexpected destination texture level pixels; 518 differences at 1 level d3d.c:2326: Test failed: Unexpected destination texture level pixels; 138 differences at 2 level d3d.c:2326: Test failed: Unexpected destination texture level pixels; 46 differences at 3 level d3d.c:2510: Test failed: Unexpected destination texture level pixels; 257 differences d3d.c:2657: Test failed: Unexpected destination texture level pixels; 256 differences at 2 level d3d.c:2657: Test failed: Unexpected destination texture level pixels; 64 differences at 3 level d3d.c:2657: Test failed: Unexpected destination texture level pixels; 16 differences at 4 level d3d.c:2657: Test failed: Unexpected destination texture level pixels; 4 differences at 5 level

1 0

Re: [PATCH] oleaut32 todo: formatting 0 with "000#"
by Marvin May 18, 2016

May 18, 2016

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

1 0

Re: [PATCH] msxml3/tests: Simplify refcount checks
by Marvin May 17, 2016

May 17, 2016

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://testbot.winehq.org/JobDetails.pl?Key=23060 Your paranoid android. === w1064 (32 bit httpreq) === httpreq.c:1628: Test failed: got 0x80070057, expected 0x00000000 === w1064 (64 bit httpreq) === httpreq.c:1628: Test failed: got 0x80070057, expected 0x00000000

1 0

Re: [PATCH v2 3/6] ddraw: Forbid creating flippable cubemaps.
by Henri Verbeet May 17, 2016

May 17, 2016

On 13 May 2016 at 13:55, Józef Kucia <jkucia(a)codeweavers.com> wrote: > + if (desc->ddsCaps.dwCaps2 & DDSCAPS2_CUBEMAP) > + { > + WARN("Tried to create a flippable cubemap.\n"); > + HeapFree(GetProcessHeap(), 0, texture); > + return DDERR_INVALIDPARAMS; > + } > + > if (desc->ddsCaps.dwCaps & DDSCAPS_TEXTURE) > { > FIXME("Flippable textures not implemented.\n"); > @@ -5748,6 +5755,8 @@ HRESULT ddraw_surface_create(struct ddraw *ddraw, const DDSURFACEDESC2 *surface_ > { > WARN("Tried to specify a back buffer count for a non-flippable surface.\n"); > HeapFree(GetProcessHeap(), 0, texture); > + if (desc->ddsCaps.dwCaps2 & DDSCAPS2_CUBEMAP) > + return DDERR_INVALIDPARAMS; > return DDERR_INVALIDCAPS; > } I suppose it ends up being more or less the same thing, but to me this looks like DDSD_BACKBUFFERCOUNT being disallowed for cubemaps rather than DDSCAPS_FLIP.

1 0

Re: [PATCH] kernel32/nls: Added SSHORTESTDAYNAME* entries
by Henri Verbeet May 17, 2016

May 17, 2016

> diff --git a/dlls/kernel32/nls/urd.nls b/dlls/kernel32/nls/urd.nls > index 65b57f7..9ce5689 100644 > --- a/dlls/kernel32/nls/urd.nls > +++ b/dlls/kernel32/nls/urd.nls > @@ -134,6 +134,13 @@ STRINGTABLE LANGUAGE LANG_URDU, SUBLANG_URDU_PAKISTAN > LOCALE_SPOSITIVESIGN "" > LOCALE_SSCRIPTS "Arab;" > LOCALE_SSHORTDATE "dd/MM/yyyy" > + LOCALE_SSHORTESTDAYNAME1 "پ" > + LOCALE_SSHORTESTDAYNAME2 "م" > + LOCALE_SSHORTESTDAYNAME3 "ب" > + LOCALE_SSHORTESTDAYNAME4 "ج" > + LOCALE_SSHORTESTDAYNAME5 "ج" I'm no expert on Urdu, but it seems suspicious to have the same abbreviation for two different days.

2 1

Re: [PATCH 2/2] include: Use inline functions for common RECT helpers.
by Alexandre Julliard May 17, 2016

May 17, 2016

Michael Stefaniuc <mstefani(a)redhat.de> writes: > Signed-off-by: Michael Stefaniuc <mstefani(a)redhat.de> > --- > dlls/user32/tests/uitools.c | 1 + > dlls/user32/uitools.c | 1 + > include/winuser.h | 38 +++++++++++++++++++++++++++++++++++--- > 3 files changed, 37 insertions(+), 3 deletions(-) Not really your fault, but this is causing some warnings here: gcc -m32 -c -o device.o device.c -I. -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe \ -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \ -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith \ -Wlogical-op -gdwarf-2 -gstrict-dwarf -fno-omit-frame-pointer -Werror -g -O2 -fno-diagnostics-show-caret device.c: In function ‘device_clear_render_targets’: device.c:393:9: error: ‘ds_rect.bottom’ may be used uninitialized in this function [-Werror=maybe-uninitialized] device.c:393:9: error: ‘ds_rect.right’ may be used uninitialized in this function [-Werror=maybe-uninitialized] cc1: all warnings being treated as errors make: *** [device.o] Error 1 -- Alexandre Julliard julliard(a)winehq.org

1 1

Re: [PATCH] winex11: Send SC_KEYMENU on managed windows.
by Marvin May 17, 2016

May 17, 2016

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://testbot.winehq.org/JobDetails.pl?Key=23042 Your paranoid android. === wvistau64 (32 bit msg) === msg.c:11039: Test failed: expected PeekMessage to return FALSE, got 1 === w864 (32 bit msg) === msg.c:6484: Test failed: Update region shouldn't be empty msg.c:6718: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6720: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6490: Test failed: Regions are different msg.c:6490: Test failed: Regions are different msg.c:6490: Test failed: Regions are different === w1064 (32 bit msg) === msg.c:6484: Test failed: Update region shouldn't be empty msg.c:6718: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6720: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6490: Test failed: Regions are different msg.c:6490: Test failed: Regions are different msg.c:6490: Test failed: Regions are different msg.c:7440: Test failed: destroy child on thread exit: 3: the msg sequence is not complete: expected 0000 - actual 001a === w1064 (64 bit msg) === msg.c:6484: Test failed: Update region shouldn't be empty msg.c:6718: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000 msg.c:6720: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:6490: Test failed: Regions are different msg.c:6490: Test failed: Regions are different msg.c:6490: Test failed: Regions are different msg.c:7440: Test failed: destroy child on thread exit: 3: the msg sequence is not complete: expected 0000 - actual 001a

1 0

Re: [PATCH 11/11] wininet: Added test of cookies with long URL.
by Marvin May 16, 2016

May 16, 2016

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://testbot.winehq.org/JobDetails.pl?Key=23039 Your paranoid android. === w1064 (32 bit internet) === internet.c:1092: Test failed: expected ret == 0, got 87 === w1064 (64 bit internet) === internet.c:1092: Test failed: expected ret == 0, got 87

1 0

Re: [PATCH 02/11] wininet: Fixed handing NULL buffer in InternetReadFileExW.
by Marvin May 16, 2016

May 16, 2016

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://testbot.winehq.org/JobDetails.pl?Key=23038 Your paranoid android. === w864 (64 bit http) === http.c:5241: Test failed: HttpSendRequest failed: 8

1 0

Re: [PATCH 01/11] wininet: Fixed internet tests on win10.
by Marvin May 16, 2016

May 16, 2016

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://testbot.winehq.org/JobDetails.pl?Key=23037 Your paranoid android. === w1064 (32 bit internet) === internet.c:1074: Test failed: expected ret == 0, got 87 === w1064 (64 bit internet) === internet.c:1074: Test failed: expected ret == 0, got 87

1 0