[Bug 53222] New: shell32:shlfolder - test_SHChangeNotify() gets unexpected WM_USER_NOTIFY messages on Windows 10

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53222

            Bug ID: 53222
           Summary: shell32:shlfolder - test_SHChangeNotify() gets
                    unexpected WM_USER_NOTIFY messages on Windows 10
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: shell32
          Assignee: wine-bugs at winehq.org
          Reporter: fgouget at codeweavers.com

shell32:shlfolder - test_SHChangeNotify() gets unexpected WM_USER_NOTIFY
messages on Windows 10. The exact failures vary a bit though:

shlfolder.c:5027: SHChangeNotify tests (0)
...
shlfolder.c:5014: RMDIR: took 2 tries
shlfolder.c:4964: verifying pidls for: RMDIR
shlfolder.c:4977: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
10)

or

shlfolder.c:4978: SHChangeNotify tests (0)
shlfolder.c:4915: verifying pidls for: MKDIR
shlfolder.c:4928: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
40000)

or

shlfolder.c:5027: SHChangeNotify tests (0)
shlfolder.c:4964: verifying pidls for: MKDIR
shlfolder.c:5014: MKDIR: took 2 tries
shlfolder.c:4964: verifying pidls for: MKDIR
shlfolder.c:4977: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
8)

or

shlfolder.c:4978: SHChangeNotify tests (1)
...
shlfolder.c:4965: CREATE: took 0 tries
shlfolder.c:4915: verifying pidls for: RMDIR
shlfolder.c:4928: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
3)

or

shlfolder.c:5014: CREATE: took 3 tries
shlfolder.c:4960: Test failed: CREATE: expected notification type 2, got: 40000
shlfolder.c:4964: verifying pidls for: CREATE
shlfolder.c:4967: Test failed: GetDisplayNameOf failed: 0x80070057
shlfolder.c:4977: Test failed: Didn't expect a WM_USER_NOTIFY message (event:
3)

https://test.winehq.org/data/patterns.html#shell32:shlfolder

The failures have been seen on Windows 10 1507, 21H1 and 21H2 but it is likely
that the other Windows 10 versions behave 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.