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

Re: [PATCH 6/7] gdiplus: Reimplement GdipCreateHBITMAPFromBitmap so it can work on locked bitmaps
by Vincent Povirk 10 Feb '17

10 Feb '17

This should probably also be tested with ImageLockModeUserInputBuf.

1 0

Re: [v6 5/6] user32: Send WM_NCPAINT and WM_ERASEBKGND when window is shown and add tests
by Marvin 09 Feb '17

09 Feb '17

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=28472 Your paranoid android. === w7u (32 bit msg) === msg.c:11986: Test failed: WmMouseHoverSeq: 0: the msg sequence is not complete: expected 0118 - actual 0000 msg.c:11988: Test failed: wrong tme.dwFlags 00000001, expected 00000000 msg.c:11988: Test failed: wrong tme.hwndTrack 0023014C, expected 00000000 msg.c:11988: Test failed: wrong tme.dwHoverTime 400, expected 0

1 0

Re: [v6 2/6] user32: Add tests for windows when first shown with SetWindowPos
by Marvin 09 Feb '17

09 Feb '17

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=28469 Your paranoid android. === w7u (32 bit msg) === msg.c:11881: Test failed: WmMouseHoverSeq: 0: the msg sequence is not complete: expected 0118 - actual 0000 msg.c:11883: Test failed: wrong tme.dwFlags 00000001, expected 00000000 msg.c:11883: Test failed: wrong tme.hwndTrack 000F018E, expected 00000000 msg.c:11883: Test failed: wrong tme.dwHoverTime 400, expected 0

1 0

Re: [PATCH] user32: Add tests for disabled buttons receiving WM_LBUTTONUP
by Marvin 09 Feb '17

09 Feb '17

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=28465 Your paranoid android. === w7u (32 bit msg) === msg.c:11637: Test failed: WmMouseHoverSeq: 0: the msg sequence is not complete: expected 0118 - actual 0000 msg.c:11639: Test failed: wrong tme.dwFlags 00000001, expected 00000000 msg.c:11639: Test failed: wrong tme.hwndTrack 000D018C, expected 00000000 msg.c:11639: Test failed: wrong tme.dwHoverTime 400, expected 0

1 0

Re: [v5 6/6] user32: Only send position-change messages when needed
by Marvin 09 Feb '17

09 Feb '17

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=28464 Your paranoid android. === wxppro (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w2003std (32 bit msg) === msg.c:5705: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 1: in msg 0x0046 expecting wParam 0x8170 got 0x8160 msg.c:5705: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 4: the msg 0x0047 was expected, but got msg 0x0022 instead msg.c:5705: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 5: the msg 0x0003 was expected, but got msg 0x0047 instead msg.c:5705: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 6: the msg 0x0005 was expected, but got msg 0x0003 instead msg.c:5705: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 11: the msg sequence is not complete: expected 0000 - actual 0005 === wvistau64 (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7u (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (64 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (64 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint

1 0

Re: [v5 5/6] user32: Send WM_NCPAINT and WM_ERASEBKGND when window is shown and add tests
by Marvin 09 Feb '17

09 Feb '17

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=28463 Your paranoid android. === wxppro (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7u (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (64 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (64 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint

1 0

Re: [v5 4/6] user32: Add WM_NCPAINT tests for windows crossing screen or maximized
by Marvin 09 Feb '17

09 Feb '17

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=28462 Your paranoid android. === wxppro (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7u (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint msg.c:7885: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:7885: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:7885: Test failed: destroy child on thread exit: 2: the msg 0x0014 was expected, but got msg 0x0082 instead msg.c:7885: Test failed: destroy child on thread exit: 3: the msg sequence is not complete: expected 0000 - actual 000f === w7pro64 (32 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (64 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (64 bit msg) === msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5223: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint

1 0

Re: [v5 3/6] user32: Add tests for windows when first shown if they have children
by Marvin 09 Feb '17

09 Feb '17

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=28461 Your paranoid android. === wxppro (32 bit msg) === msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (32 bit msg) === msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7u (32 bit msg) === msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (32 bit msg) === msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === wvistau64 (64 bit msg) === msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint === w7pro64 (64 bit msg) === msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 2: the msg 0x0085 should have been sent by BeginPaint msg.c:5148: Test failed: SetWindowPos:show_popup_first_show_window_child2: 3: the msg 0x0014 should have been sent by BeginPaint

1 0

Re: [v5 2/6] user32: Add tests for windows when first shown with SetWindowPos
by Marvin 09 Feb '17

09 Feb '17

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=28460 Your paranoid android. === w7u (32 bit msg) === msg.c:11859: Test failed: WmMouseHoverSeq: 0: the msg sequence is not complete: expected 0118 - actual 0000 msg.c:11861: Test failed: wrong tme.dwFlags 00000001, expected 00000000 msg.c:11861: Test failed: wrong tme.hwndTrack 00130188, expected 00000000 msg.c:11861: Test failed: wrong tme.dwHoverTime 400, expected 0

1 0

Re: [v5 1/6] user32: Add tests for windows when first shown with WS_VISIBLE or RedrawWindow
by Marvin 09 Feb '17

09 Feb '17

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=28459 Your paranoid android. === w2008s64 (32 bit msg) === msg.c:5408: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 1: in msg 0x0046 expecting wParam 0x8170 got 0x8160 msg.c:5408: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 4: the msg 0x0047 was expected, but got msg 0x0022 instead msg.c:5408: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 5: the msg 0x0003 was expected, but got msg 0x0047 instead msg.c:5408: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 6: the msg 0x0005 was expected, but got msg 0x0003 instead msg.c:5408: Test failed: ShowWindow(SW_SHOWMINNOACTIVE) child with invisible parent: 11: the msg sequence is not complete: expected 0000 - actual 0005 === w7u (32 bit msg) === msg.c:7588: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000

1 0