Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53176
1) The async test is broken on Windows 10 1507. This appears to be a trend among WinRT dlls. I'm thinking that we can add macro definitions for each testbot VM to avoid having to skip tests that would otherwise be working fine, and just greater control over tests in general.
2) The provider file that contains `interface IWineAsyncInfoImpl` is likely going to be reused again in the future. Perhaps a new file can be added in the include/wine folder to prevent duplicate code? I can do this in a separate merge request and cleanup the existing provider files.
3) All the check_bool_async tests return a random async_id so I skipped them. Testbot example: https://testbot.winehq.org/JobDetails.pl?Key=127232&f208=exe32.report#k208
--
v8: cryptowinrt/tests: Add IKeyCredentialManagerStatics_IsSupportedAsync tests.
cryptowinrt: Implement IKeyCredentialManagerStatics_IsSupportedAsync.
cryptowinrt: Import IAsyncOperation from windows.gaming.input.
cryptowinrt: Stub IKeyCredentialManagerStatics interface.
cryptowinrt: Add private.h file.
cryptowinrt/tests: Add ICryptographicBufferStatics interface test.
include: Add windows.security.credentials.idl file.
https://gitlab.winehq.org/wine/wine/-/merge_requests/1714
SetInputType tests will randomly failed after PATCH 3 (It was OK in PATCH 2). I spend many time on figuring out why. And I found a weird thing: If I comment out the compare_nv12() in check_dmo_output_data_buffer_(), the test failures will be gone.
I can't think out the reason. I don't understand why compare_nv12() in check_dmo_output_data_buffer_() affects SetInputType tests. And I don't want to waste too much time on the test stuff. Implementing the decoder is more important, so I marked the failed tests as flaky.
--
v2: mf/tests: Test output data for WMV decoder DMO.
mf/tests: Test ProcessInput and ProcessOutput for WMV decoder DMO.
mf/tests: Correctly initialize DMO media type.
https://gitlab.winehq.org/wine/wine/-/merge_requests/2247
This series intent is to let winedbg (and dbghelp) load the 64bit PE modules
of a wow64 debuggee.
At this stage, all debug info of all modules (PE and ELF) are properly loaded
(and displayed with 'info wow share' command).
Breakpoint and backtrace in 64bit code of a wow64 debuggee are not available.
The serie contains:
- extension of tests to show that 64bit load dll events are generated for
a wow64 debuggee (for a 64bit debugger, not for a 32bit one)
- change for adapting filtering of events
I opted for doing it in ntdll and passing the machine of the mapping in
request's reply. Please advisde if you'd prefer another approach.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/2240
--
v4: vkd3d-shader/hlsl: Support case-insensitive lookup for builtin 'float' type.
vkd3d-shader/hlsl: Use unsigned type for the 'dword' alias.
vkd3d-shader/hlsl: Support case-insensitive lookup for builtin 'dword' type.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/101