February 2016 - Wine-devel - list.winehq.org

Re: [PATCH] advapi32, ntdll: Skip test_redirection tests if there is not enough privileges
by Marvin 17 Feb '16

17 Feb '16

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=20600 Your paranoid android. === build (build) === Patch failed to apply

1 0

[GSoC Things] Want to make wpcap.dll become more usable on wine
by Jianqiu Zhang 17 Feb '16

17 Feb '16

Hi, I am working on improving and implementing more functions for wpcap.dll on wine wpcap is the Windows version of pcap, Packet Capture Library for wireshark and other network analyzing software, I have done some research on it, In wine we cannot use the windows kernel driver, but winpcap actually use it, so I follow the wine wpcap code and try to add more wrapper to wpcap, Here is the patch I' ve submitted and was add to wine-staging, https://github.com/wine-compholio/wine-staging/tree/master/patches/wpcap-Se… One of the most difficult point is , there aren't many applications using wpcap.dll, I cannot found plenty of them, According to fracting(Hong Qian) 's suggestions, Dr.com , a Client for many Chinese university students to gain access to cernet uses wpcap, If wpcap.dll can improved to make it available for Dr.Com , maybe many university students using Linux can gain access to cernet. I will try to improve wpcap.dll in two different ways: 1. Use wine wpcap.dll , and write wrappers 2. Write packet.dll which is needed by native wpcap.dll, and then use native wpcap.dll I will write testcase for the new dll packet.dll. Is there andy sugesstions on this idea? Any suggesstions are appreciated Thanks Jianqiu

3 3

Re: [PATCH] usp10/tests: Use todo_wine_if() in tests
by Marvin 16 Feb '16

16 Feb '16

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=20594 Your paranoid android. === w1064 (32 bit usp10) === usp10.c:1423: Test failed: 0: uJustification incorrect (0) usp10.c:1423: Test failed: 1: uJustification incorrect (0) usp10.c:1423: Test failed: 2: uJustification incorrect (0) usp10.c:1423: Test failed: 3: uJustification incorrect (0) usp10.c:1423: Test failed: 4: uJustification incorrect (0) usp10.c:1423: Test failed: 5: uJustification incorrect (0) usp10.c:1423: Test failed: 6: uJustification incorrect (0) usp10.c:1423: Test failed: 7: uJustification incorrect (0) usp10.c:1423: Test failed: 8: uJustification incorrect (0) usp10.c:1423: Test failed: 9: uJustification incorrect (0) usp10.c:1439: Test failed: 3: uJustification incorrect (0) usp10.c:1439: Test failed: 5: fDiacritic incorrect (1) usp10.c:1439: Test failed: 5: fZeroWidth incorrect (1) usp10.c:1439: Test failed: 15: fDiacritic incorrect (1) usp10.c:1439: Test failed: 15: fZeroWidth incorrect (1)

1 0

Re: [PATCH] wininet/tests: Use todo_wine_if() in tests
by Marvin 16 Feb '16

16 Feb '16

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=20593 Your paranoid android. === w1064 (32 bit internet) === internet.c:1507: Test failed: Got 0, expected 1223 (12042) internet.c:1512: Test failed: Got 0, expected 1223 (12042) internet.c:1521: Test failed: Got 0, expected 1223 (12042) internet.c:1074: Test failed: expected ret == 0, got 87

1 0

Re: [PATCH] ws2_32/tests: Use todo_wine_if() in tests
by Marvin 16 Feb '16

16 Feb '16

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=20591 Your paranoid android. === w7pro64 (32 bit sock) === sock.c:7731: Test failed: bytesReturned isn't supposed to be 1 sock.c:7777: Test failed: Waiting for timeout failed with 0 + errno 997

1 0

Re: [v2] d3d8/tests: Use todo_wine_if() in tests
by Marvin 16 Feb '16

16 Feb '16

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=20589 Your paranoid android. === w1064 (32 bit device) === device.c:2725: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2730: Test failed: The focus window is active. device.c:2738: Test failed: Got unexpected hr 0x88760869. device.c:2742: Test failed: Got unexpect screen size 800x600. device.c:2757: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2766: Test failed: Got unexpect screen size 800x600. device.c:2779: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2787: Test failed: Got unexpect width 640. device.c:2788: Test failed: Got unexpect height 480.

1 0

Re: [v2] d3d9/tests: Use todo_wine_if() in tests
by Marvin 16 Feb '16

16 Feb '16

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=20588 Your paranoid android. === w1064 (32 bit d3d9ex) === d3d9ex.c:2347: Test failed: Got unexpected hr 0, i=0. d3d9ex.c:2349: Test failed: Got unexpected hr 0, i=0. d3d9ex.c:2347: Test failed: Got unexpected hr 0, i=1. d3d9ex.c:2349: Test failed: Got unexpected hr 0, i=1.

1 0

Re: [PATCH 6/6] d3d11/tests: Test relative addressing in constant buffers.
by Marvin 16 Feb '16

16 Feb '16

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=20572 Your paranoid android. === wvistau64 (32 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 74199C9F === w2008s64 (32 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 74179C9F === wvistau64 (64 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 0000000074AAFCBB === w2008s64 (64 bit d3d11) === d3d11.c:5365: Test failed: Failed to create vertex shader, hr 0x80070057. d3d11.c:5367: Test failed: Failed to create pixel shader, hr 0x80070057. d3d11: unhandled exception c0000005 at 0000000073DAFCBB

1 0

Re: [v4] shell32: fix two bugs in IQueryAssocations
by Marvin 16 Feb '16

16 Feb '16

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=20568 Your paranoid android. === w2003std (32 bit assoc) === assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x0 assoc.c:174: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x0 assoc.c:178: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x80070483 assoc.c:183: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x80070483 assoc.c:184: Test failed: assoc.c:122: Test failed: GetString returned 0x80070002, expected 0x80070483 assoc.c:185: Test failed:

2 1

Re: d3d9/tests: Use todo_wine_if() in tests
by Henri Verbeet 16 Feb '16

16 Feb '16

On 16 February 2016 at 12:31, Frédéric Delanoy <frederic.delanoy(a)gmail.com> wrote: > Signed-off-by: Frédéric Delanoy <frederic.delanoy(a)gmail.com> > --- > dlls/d3d9/tests/device.c | 20 ++++---------------- > dlls/d3d9/tests/visual.c | 22 ++++------------------ > 2 files changed, 8 insertions(+), 34 deletions(-) > Why did you do this for some tests, but not others? (E.g. you modify test_window_style() for d3d9, but not for d3d9ex.)

2 1