[Bug 48820] New: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures
https://bugs.winehq.org/show_bug.cgi?id=48820 Bug ID: 48820 Summary: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The TestBot's w1064v1809-zh_CN configuration runs the tests on Windows 10 1809 in a Chinese locale. This test configuration gets unique failures in user32:win: win.c:3852: Test failed: hwnd 007404D2 message 7fff win.c:3858: Test failed: message 7fff available win.c:3931: Test failed: hwnd 007404D2/0054050A message 7fff win.c:3934: Test failed: hwnd 007404D2/0054050A message 7fff Note how these messages are very similar to the IME messages in bug 48819. However 0x7fff is a totally unknown message: all I can say about it is that it's WM_APP-1. So maybe it's another IME system. Maybe not? See: https://test.winehq.org/data/tests/user32:win.html However note that quite often WineTest fails to submit its results to test.winehq.org, typically because it times out. So you can more easily find the latest failure by looking for the "32 bit WineTest: base VMs" jobs on the TestBot. Finally, three of these messages include the window handles which means they are "always new". Because of this the TestBot will mistakenly attribute the failure to any user32 patch submitted to wine-devel, which should cause them to be rejected. So I bumped the priority on this bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- The relevant TestBot configuration is w1064v1809-ja of course :-( -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- For some unknown reason this is not happening anymore. https://test.winehq.org/data/patterns-tb-win.html -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de Status|RESOLVED |CLOSED --- Comment #3 from André H. <nerv(a)dawncrow.de> --- closing worksforme -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |--- Status|CLOSED |REOPENED --- Comment #4 from François Gouget <fgouget(a)codeweavers.com> --- Actually this is still happening: https://test.winehq.org/data/patterns.html#user32:win The relevant TestBot VM is now w10pro64-ja. I'm not sure why the failure stopped happening for a while last summer but the unexpected "message 7fff available" failures have been happening systematically in the past 40-ish builds. I've had issues where the UserDefaultLCID locale would sometimes not stick when configuring the test VMs. Maybe that's why the failure disappeared for a while. The locale-setting issue should soon be fixed so we will know for sure then. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 --- Comment #5 from François Gouget <fgouget(a)codeweavers.com> --- Here is a more recent set of failures from a recent run on w10pro64-ja. Notice the additional 0287 (???), 0201 (WM_LBUTTONDOWN) and 0203 (WM_LBUTTONDBLCLK) messages: win.c:4514: Test failed: hwnd 0000000000170456 message 7fff win.c:4520: Test failed: message 7fff available win.c:4549: Test failed: hwnd 00000000001A0348/0000000001BB00F4 message 0287 win.c:4554: Test failed: hwnd 00000000001A0348/0000000001BB00F4 message 0287 win.c:4559: Test failed: hwnd 0000000001BB00F4/0000000001BB00F4 message 0201 win.c:4568: Test failed: message 0203 available win.c:4580: Test failed: hwnd 00000000001A0348/00000000005E0474 message 0287 win.c:4584: Test failed: hwnd 00000000001A0348/00000000005E0474 message 0287 win.c:4593: Test failed: hwnd 0000000000170456/0000000001BB00F4 message 7fff win.c:4596: Test failed: hwnd 0000000000170456/0000000001BB00F4 message 7fff win.c:4629: Test failed: hwnd 00000000001A0348/0000000001BE0466 message 0287 win.c:4631: Test failed: wparam 32 win.c:4635: Test failed: hwnd 00000000001A0348/0000000001BE0466 message 0287 win.c:4642: Test failed: hwnd 0000000001BE0466/0000000001BE0466 message 0201 win.c:4659: Test failed: message 0203 available -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48820 --- Comment #6 from François Gouget <fgouget(a)codeweavers.com> --- These messages actually match exactly those from bug 51395 about the failures in the Korean locale. Both the Korean and Japanese locales are installed in that VM so maybe the messages match because the wrong IME is active? Or both IMEs now work the same way. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla