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

Re: [3/6] user32/tests: Reenable test function for WM_GETTEXT.
by Marvin Nov. 18, 2014

Nov. 18, 2014

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=10317 Your paranoid android. === w2008s64 (64 bit win) === win.c:3367: Test failed: hwnd 00000000000100F4 message 0118

2 1

Re: configure: Fix detection of gnutls on Ubuntu 14.10.
by Nicolas Le Cam Nov. 18, 2014

Nov. 18, 2014

2014-11-17 9:37 GMT+01:00 Sebastian Lackner <sebastian(a)fds-team.de>: > Someone asked me to submit this, although its very Ubuntu specific. > > On some Ubuntu versions there only exists a package where libgnutls was renamed to libgnutls-deb0. As an effect ./configure fails to detect it properly because it compares the exact soname. > > http://packages.ubuntu.com/precise/amd64/libgnutls28/filelist > http://packages.ubuntu.com/utopic/amd64/libgnutls-deb0-28/filelist > > --- > configure.ac | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > > Hi Sebastian, This also fixes libgnutls detection on Debian testing (and futur Jessie) and derivatives. What about [[libgnutls\\(-deb[[0-9]]\\)\\{0,1\\}]] or [[libgnutls\\(-[[0-9A-Za-z]]\+\\)\\{0,1\\}]] instead. I don't think the debian specific soname will bump too often but it could avoid the need for another patch. -- Nicolas Le Cam

2 1

Re: [PATCH 4/6] d3d8/tests: Test style changes on focus loss.
by Marvin Nov. 17, 2014

Nov. 17, 2014

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=10310 Your paranoid android. === w8 (32 bit device) === device.c:1181: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1226: Test failed: Reset failed, hr 0x88760868. device.c:1228: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1232: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1239: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1240: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1241: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1242: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1243: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1244: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1249: Test failed: Screen width is 640, expected 800. device.c:1250: Test failed: Screen height is 480, expected 600. device.c:1256: Test failed: Back buffer width is 640, expected 800. device.c:1258: Test failed: Back buffer height is 480, expected 600. device.c:1288: Test failed: Screen width is 640, expected 1024. device.c:1289: Test failed: Screen height is 480, expected 768. device.c:2364: Test failed: Expected message 0x46 for window 0, but didn't receive it. device.c:2369: Test failed: The focus window is active. device.c:2373: Test failed: Got unexpected hr 0. device.c:2379: Test failed: Got unexpected hr 0. device.c:2393: Test failed: Got unexpected hr 0. device.c:2523: Test failed: Expected foreground window 000501B8, got 0002004C. device.c:2899: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2903: Test failed: Expected device window extended style 0x108, got 0x100. device.c:2926: Test failed: Failed to reset device, hr 0x88760868. device.c:2930: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2934: Test failed: Expected device window extended style 0x108, got 0x100. device.c:2948: Test failed: Failed to set foreground window. device.c:2952: Test failed: Expected device window style 0x34cf0000, got 0x4cf0000. device.c:2956: Test failed: Expected device window extended style 0x108, got 0x100.

1 0

Re: [PATCH 3/6] d3d8/tests: Test messages on focus loss (v2).
by Marvin Nov. 17, 2014

Nov. 17, 2014

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=10309 Your paranoid android. === w8 (32 bit device) === device.c:1181: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1226: Test failed: Reset failed, hr 0x88760868. device.c:1228: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1232: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1239: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1240: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1241: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1242: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1243: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1244: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1249: Test failed: Screen width is 640, expected 800. device.c:1250: Test failed: Screen height is 480, expected 600. device.c:1256: Test failed: Back buffer width is 640, expected 800. device.c:1258: Test failed: Back buffer height is 480, expected 600. device.c:1288: Test failed: Screen width is 640, expected 1024. device.c:1289: Test failed: Screen height is 480, expected 768. device.c:2364: Test failed: Expected message 0x46 for window 0, but didn't receive it. device.c:2369: Test failed: The focus window is active. device.c:2373: Test failed: Got unexpected hr 0. device.c:2379: Test failed: Got unexpected hr 0. device.c:2393: Test failed: Got unexpected hr 0. device.c:2523: Test failed: Expected foreground window 000B00CA, got 0002004C. device.c:2898: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2902: Test failed: Expected device window extended style 0x108, got 0x100. device.c:2925: Test failed: Failed to reset device, hr 0x88760868. device.c:2929: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2933: Test failed: Expected device window extended style 0x108, got 0x100. device.c:3301: Test failed: Failed to reset device. device.c:3308: Test failed: Expected {0, 0, 1024, 768}, got {0, 0, 512, 384}. device.c:3316: Test failed: Expected wndproc != 0x411620.

1 0

Re: cryptext: add stubs for CryptExtAddPFX/CryptExtAddPFXW
by Nikolay Sivov Nov. 17, 2014

Nov. 17, 2014

On 17.11.2014 22:21, Austin English wrote: > +HRESULT WINAPI CryptExtAddPFX(LPCSTR filename) > +{ > + FIXME("stub: %s\n", debugstr_a(filename)); > + return ERROR_CALL_NOT_IMPLEMENTED; > +} Return type and error code don't match here. If it should be HRESULT use E_NOTIMPL, otherwise return type should be DWORD or similar.

1 0

Re: [PATCH 2/2] mshtml: Added IHTMLStyleSheet::cssText tests.
by Marvin Nov. 17, 2014

Nov. 17, 2014

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=10298 Your paranoid android. === w2000pro (32 bit dom) === dom: unhandled exception c0000005 at 780104AC

1 0

Re: [PATCH 2/7] d3d9/tests: Test messages on focus loss.
by Alexandre Julliard Nov. 17, 2014

Nov. 17, 2014

Stefan Dösinger <stefan(a)codeweavers.com> writes: > Resolution changing behavior will be tested in a separate patch. > --- > dlls/d3d9/tests/d3d9ex.c | 277 ++++++++++++++++++++++++++++---------------- > dlls/d3d9/tests/device.c | 293 +++++++++++++++++++++++++++++++---------------- > 2 files changed, 375 insertions(+), 195 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M d3d9.dll -p d3d9_test.exe.so d3d9ex && touch d3d9ex.ok d3d9ex.c:1656: Tests skipped: This GPU supports SM3, skipping unsupported shader test. d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=0. d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=0. d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=1. d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=1. make: *** [d3d9ex.ok] Error 4 -- Alexandre Julliard julliard(a)winehq.org

2 3

Re: [PATCH 5/5] d3d10core/tests: Port alpha_test() to d3d10core.
by Marvin Nov. 17, 2014

Nov. 17, 2014

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=10295 Your paranoid android. === w8 (32 bit visual) === visual.c:2635: Test failed: unexpected colortable on offscreen surface

1 0

Re: Update on MSNet
by Susan Cragin Nov. 14, 2014

Nov. 14, 2014

You can now ask that or any other question. I just asked about the licenses, Page 6. http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.a…

2 1

Update on MSNet
by Susan Cragin Nov. 14, 2014

Nov. 14, 2014

I'm sure you know this, but thought I would pass this along. MSNet framework is open-source. http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.a… An article I read said that MS has committed to developing linux and mac versions, but I don't see where MS has committed money to it. Keep up the good work! Susan

3 2