https://bugs.winehq.org/show_bug.cgi?id=53222
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |piotr@codeweavers.com
--- Comment #1 from François Gouget fgouget@codeweavers.com --- There is also a variant with an unexpected notification type:
shlfolder.c:5057: SHChangeNotify tests (0) ... shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 shlfolder.c:4994: verifying pidls for: RMDIR shlfolder.c:4997: Test failed: GetDisplayNameOf failed: 0x80070057 shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 3) shlfolder.c:5044: RMDIR: took 0 tries
Where: 0x10 == SHCNE_RMDIR 0x40000 == SHCNE_FREESPACE 0x80070057 == E_INVALIDARG and for older failure modes: 0x1 == SHCNE_RENAMEITEM 0x2 == SHCNE_CREATE 0x8 == SHCNE_MKDIR
SHCNE_FREESPACE indicates that the amount of free space on the drive has changed. So I guess that means some other process on the machine wrote some file and our test was not prepared to receive this type of notification.
Our test should find a way to be more specific about the notifications it is interested in (is requesting notifications only for a specific directory possible?); or it should simply ignore all notifications that don't match one of our test paths; or retry a few times and hope really hard that Windows Defender or some other background task did not decide to do some maintenance while the test is running.