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

Re: user32: Change SetForegroundWindow behavior on windows with parent and no WS_CHILD flag
by Marvin March 27, 2014

March 27, 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=6025 Your paranoid android. === w8 (32 bit win) === win.c:6433: Test failed: 0x80/0x1c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6455: Test failed: 0x80/0x1010000: window rect 0,0-1024,768 win.c:6433: Test failed: 0x80/0x81c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6433: Test failed: 0/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6433: Test failed: 0x40000/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6433: Test failed: 0x80/0x41c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6433: Test failed: 0x80/0x1c50000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6455: Test failed: 0x80/0x1050000: window rect 0,0-1024,768 win.c:6433: Test failed: 0x80/0x1c10000: window rect 0,0-1024,768 must be in 0,0-1024,728 win.c:6455: Test failed: 0x80/0x1410000: window rect 0,0-1024,768 win.c:6216: Test failed: wrong error 31

1 0

Re: loader: Add registry keys for Hidden and HideFileExt.
by Alexandre Julliard March 26, 2014

March 26, 2014

Rico Schüller <kgbricola(a)web.de> writes: > --- > loader/wine.inf.in | 2 ++ > 1 file changed, 2 insertions(+) It breaks the tests: ../../../tools/runtest -q -P wine -T ../../.. -M shell32.dll -p shell32_test.exe.so shlfolder && touch shlfolder.ok shlfolder.c:817: Test failed: SetNameOf failed! hr = 80004005 make: *** [shlfolder.ok] Error 1 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: user32: Change SetFocus behavior on windows with parent and no WS_CHILD flag
by Marvin March 26, 2014

March 26, 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=6004 Your paranoid android. === w8 (32 bit win) === win.c:6205: Test failed: wrong error 31

1 0

Re: [PATCH 10/10] d3d9/tests: Use a separate device for alphatest_test().
by Marvin March 26, 2014

March 26, 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=6001 Your paranoid android. === w8 (32 bit visual) === visual.c:7387: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7372: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7372: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0

Re: [PATCH 09/10] d3d9/tests: Use a separate device for viewport_test().
by Marvin March 26, 2014

March 26, 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=6000 Your paranoid android. === w8 (32 bit visual) === visual.c:7387: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7372: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7372: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0

Re: [PATCH 08/10] d3d9/tests: Use a separate device for test_constant_clamp_vs().
by Marvin March 26, 2014

March 26, 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=5999 Your paranoid android. === w8 (32 bit visual) === visual.c:7387: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7372: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7372: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0

Re: [PATCH 07/10] d3d9/tests: Use a separate device for test_compare_instructions().
by Marvin March 26, 2014

March 26, 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=5998 Your paranoid android. === w8 (32 bit visual) === visual.c:7357: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7342: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7342: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0

Re: [PATCH 06/10] d3d9/tests: Use a separate device for test_mova().
by Marvin March 26, 2014

March 26, 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=5997 Your paranoid android. === w8 (32 bit visual) === visual.c:7325: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7310: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7310: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0

Re: [PATCH 05/10] d3d9/tests: Use a separate device for loop_index_test().
by Marvin March 26, 2014

March 26, 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=5996 Your paranoid android. === w8 (32 bit visual) === visual.c:7297: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0

Re: [PATCH 04/10] d3d9/tests: Use a separate device for sincos_test().
by Marvin March 26, 2014

March 26, 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=5995 Your paranoid android. === w8 (32 bit visual) === visual.c:7297: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00 visual.c:7282: Test failed: Input test: Quad 2(1crd) returned color 0x00000000, expected 0x00ffff00

1 0