The table size typically keeps increasing such that in some cases the
size we got is already too small by the time we try to get the table
content in the next iteration.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54328
On windows, we get some test failures as un-expected thread
create debug events are sent.
Try to filter them out in a couple of places.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
Current test in debugger expects that all breakpoint debug
events appear before all the exit thread events.
On Windows, it happens that sometimes the breakpoint and exit
thread events are intertwined (making the test fail).
So, this patch:
- merges the exception events loop and the exit thread events loop
into a single loop.
- detects the unordered sequence (mark it broken as windows only)
- extends the test so that we check that all exit thread events
are received.
- introduce next_event_filter helper to not return some unwanted
events.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47874
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
Instead of using glBufferSubData(). In practice, this means that we will either
discard and rename the BO (if it's still in use) or write directly into it (if
not).
This improves performance drastically on NVidia GL drivers.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53408
Analogous to the Vulkan backend.
This is not particularly impactful, though, since it only affects buffer-buffer
copies in the case where ARB_copy_buffer is not supported.
The tests are actually racy, and the async operation is cancellable in
a very short period of time after its creation, but before it started
executing.
This will be hard to test precisely and it's not related to dinput tests
in any way. Let's remove this to fix some spurious Windows failures.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54283
To match combase allocations, as for instance we're freeing pointers
returned from InternalIrotRevoke, which are allocated using combase
MIDL_user_allocate.
Some window managers have trouble moving fullscreen windows to another monitor. For example, KWin
doesn't allow moving windows with _NET_WM_STATE_FULLSCREEN set. FVWM used by TestBots keeps
the size for fullscreen windows after they are moved to another monitor and when the window is also
fullscreen on the new monitor, which could be a bug in FVWM. But let's work around this in the tests
as well. The changed tests don't need created windows being fullscreen at the start.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54172
