I have been investigating the ole32:clipboard, user32:clipboard and user32:edit failures because they seemed to have a common outside cause, namely the Radeon Windows driver.
But user32:clipboard also sometimes has similar failures in Wine on my box. So I will start with these.
Here is one exemple happening in test_synthesized():
clipboard.c:817: 0024: CloseClipboard() = 1 # the test closed the clipboard
00a4:trace:clipboard:acquire_selection win e000010 00a4:trace:clipboard:X11DRV_SelectionRequest got request on e000010 for selection "CLIPBOARD" target "TARGETS" win bc00001 prop "SELECTION_DATA" # 00a4 is the winex11.drv thread for the clipboard manager # here it got an X11 message
... 00a4:trace:clipboard:OpenClipboard 00010040 == clipboard_hwnd 00a4:trace:clipboard:GetClipboardData CF_TEXT sending WM_RENDERFORMAT to 0005004A
0024:trace:clipboard:CountClipboardFormats returning 4 0024:trace:clipboard:IsClipboardFormatAvailable CF_TEXT -> 1 0024:trace:clipboard:IsClipboardFormatAvailable CF_LOCALE -> 1 0024:trace:clipboard:IsClipboardFormatAvailable CF_OEMTEXT -> 1 0024:trace:clipboard:IsClipboardFormatAvailable CF_UNICODETEXT -> 1 # back to the main test thread
0024:trace:clipboard:OpenClipboard 00000000 clipboard.c:832: 0024: OpenClipboard(00000000) = 0 (open=00010040 own=0005004A) clipboard.c:833: Test failed: 0: gle 5 # the test's OpenClipboard() call fails because winex11.drv has not # released the clipboard yet.
... 00a4:trace:clipboard:GetClipboardData CF_TEXT error c0000034 00a4:trace:clipboard:GetClipboardData CF_UNICODETEXT error c0000034 00a4:trace:clipboard:CloseClipboard
Why did winex11.drv get a query for the clipboard content? Based on other X11 requests I blame KDE's clipboard manager:
00a4:trace:clipboard:X11DRV_SelectionRequest got request on e000010 for selection "CLIPBOARD" target "TARGETS" win 2000013 prop "_QT_SELECTION"
So this explains why it happens on my box and not in the TestBot's VM since they run fvwm and have no clipboard manager.
What should we do about that?