- wine-devel - winehq.org

Wine staging 7.18 release
by Alistair Leslie-Hughes 23 Sep '22

23 Sep '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.18 (514 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ws2_32: Return a valid value for WSAIoctl SIO_IDEAL_SEND_BACKLOG_QUERY. * dwrite: Test IDWriteTextFormat with nonexistent font. * dwrite: Use MapCharacters for non-visual characters. * dwrite: Use MapCharacters for dummy line metrics. Added: * None Updated: * server-unix_name * ntdll-Junction_Points Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

What macOS SDK is being tested against on gitlab?
by Dean Greer 23 Sep '22

23 Sep '22

Hi everyone, I’d just tried to build the current git and winemac.drv is failing building on macOS Monterey with the latest 12.3 SDK so I’m assuming the gitlab test is using an older macOS SDK?

3 10

How to test out wines WoW64?
by Dean Greer 23 Sep '22

23 Sep '22

Hi everyone, Since there now seems to be support within winex11.drv and winemac.drv what patches are now required to make use of the WoW64 work? I'd like to have this enabled within the macOS packages as soon as possible even if that means possibly carrying some patches locally for a while, ideally having a way to build the contents of i386-windows without needing to build i386-unix.

2 3

[vkd3d] Handling object components within the HLSL compiler.
by Francisco Casas 20 Sep '22

20 Sep '22

Hello, I write this update on what I am working on, because I think it introduces some architectural changes that may be good to discuss, or at least mention. Sorry if this text is a bit dense, I hope to send all this as a merge request in a couple of days from now. Albeit we may want to avoid merging before the code freeze ends. More than a week ago, I started trying to implement SM1 resource loads. For this, in particular, it is necessary to infer each sampler's dimensions from usage (a use in a tex2D implies that the sampler is 2D, if not previously declared as such). This gets complicated when there are arrays of samplers, because each sampler component can have a different dimension, and yet being part of the same variable. For solving this I tried introducing a field to allow us to store data for each component within hlsl_ir_var. But this turned to be a complicated solution. As now, we lost the component information in the derefs once we start working with register offsets. I also wanted to have per-component data because I realized that, in general, we are not handling object components properly when they are part of a larger array/struct. But then I thought on an alternative solution: adding a compiler pass to promote each object component within a large variable to a new standalone variable, and prepend a store from this standalone variable to the the original path of the component within the large variable; relying on copy-prop and dce so that all references that refer to these components end up pointing to the new standalone variable. This allows us to use the fields of the hlsl_ir_var (in particular, the register allocation) for each object component, which solves the problem. While that strategy works, I then realized that we cannot use it when targeting SM1 profiles, because we wouldn't be replicating the CTAB (which doesn't introduce a new variable for each component in multi-dimensional object arrays, just increases its register size). SM4 on the other hand seems to do this, separating each sampler and texture as its own variable in the RDEF block. My conclusion then, is that it is a good idea to separate each object component into its own variable in SM4 (as long they are named with the correct subscripts, like "foo.tex[3]"). And while we can't do that in SM1, the good news is that SM1 doesn't allow objects as components of larger types except within (possible multi-dimensional) arrays. Samplers and Textures cannot be components of structs within SM1 profiles, so we only have to support those cases in hlsl_sm1.c. This approach also has the benefit that now, all the component register allocation information should be representable using the fields in the hlsl_ir_var struct and the register size data within hlsl_type [1], since each variable should only care about a single register type now. Storing register allocation data component-wise should not be necessary. So I am implementing a series of patches to ensure that: * When targeting SM4 profiles, all object components are separated into a sole variable. * When targeting SM1 profiles, it is not allowed to declare objects as components of structs; so they will either be a sole variable, or belong to either a (possibly multi-dimensional) array of elements of the same type, as declared within the shader. * SM1 resource loads work. My plan for this series, in terms of patches is: * Parse the tex3D() intrinsic. (already made by zf) * Parse the tex2D() intrinsic. (already made by zf) * Validate that object are not components of structs in SM1. * Properly allocate registers for object arrays for SM1. * Infer sampler register dimensions and write declarations in SM1. * Write resource loads in SM1. * Separate objects as standalone variables in SM4. * Lower combined samplers to separate sampler and texture objects for SM4. (already made by zf) * Lower separate sampler and texture objects to combined samplers for SM1. (already made by zf) It remains to check if object arrays are handled properly in the last two [2], or modify these patches accordingly. Best regards, Francisco. --- [1] I know we intend to remove this field later, when we move register allocation to each sm*_write.c, but I think we probably want to replace those precomputed register offset fields with equivalent SM-specific functions that retrieve the register offset for each component. [2] In SM1 profiles, when there are texture arrays and they are used together with samplers, only one variable is created (not one for each pair of components). This is allowed: ``` Texture2D tex[3][2]; sampler sam; float4 main() : SV_TARGET { return tex[0][1].Sample(sam, float2(1, 2)) + tex[1][0].Sample(sam, float2(1, 2)); } ``` This is allowed (but "not yet implemented" in fxc 9 and 10) ``` Texture2D tex; sampler sam[2][3]; float4 main() : SV_TARGET { return tex.Sample(sam[0][2], float2(1, 2)) + tex.Sample(sam[1][0], float2(1, 2)); } ``` This is not allowed: ``` Texture2D tex[3]; sampler sam[4]; float4 PSMain() : SV_TARGET { return tex[1].Sample(sam[1], float2(1, 2)) + tex[2].Sample(sam[0], float2(1, 2)); } ``` gives: ``` error X4581: Cannot use texture arrays on DX9 targets with multiple samplers. ```

2 5

Request for new 7.0 stable release
by Nick Sarnie 18 Sep '22

18 Sep '22

Hi, I'm part of the Wine packaging team for Gentoo. We noticed that the 7.0.x stable branch is currently at 7.0, and the 6.0.x stable branch has had some maintenance releases after the release of 7.0, so there have been some bug fixes backported to 6.0.x (e.g. 6.0.4) that are not available in the 7.0 stable release. Would the Wine team be willing to do a maintenance release for the 7.0.x branch to include these bug fixes (and possibly others)? If not, would you please explain the rationale behind that decision and the intended stable branch release cadence? Thanks for your time, Sarnex

2 2

WineHQ.org Downtime
by Jeremy Newman 12 Sep '22

12 Sep '22

The WineHQ.org server will be down for maintenance and upgrades starting today 2022-09-12 at 13:00 CDT (GMT-5) This downtime will be a minimum of 30 minutes, but could take longer depending on any issues that arise. This will take offline all mailing lists and websites during the maintenance timeframe. After the maintenance is complete, various services may take longer to come back online or may exhibit unexpected behavior. We will be fixing these issues are quickly as we can. Thanks for your patience and I will reply back to this thread if anything changes. I will also be online on the #winehackers IRC room. -N

1 1

Re: fixing some fixme code
by Jin-oh Kang 12 Sep '22

12 Sep '22

Forwarding to wine-devel. Please remember to use the "reply all" button next time. Thank you! On Mon, Sep 12, 2022, 11:11 AM Owen Hogarth <gurenchan(a)gmail.com> wrote: > Hello guys, I am trying to get this program; R Trader Pro to work on Linux. > I installed winetricks and then I received some different errors. > > I would like to fix the problem but I would also like to avoid doing > unnecessary work, that's why I am asking on the development mailing list. > > Here's the new error log, is it possible to get the program working? > 017c:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0174:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0174:fixme:file:NtLockFile I/O completion on lock not implemented yet > 0174:fixme:ntdll:NtQuerySystemInformation info_class > SYSTEM_PERFORMANCE_INFORMATION > 0194:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:imm:ImeSetActiveContext (0x2ca590, 1): stub > 0174:fixme:imm:ImmReleaseContext (0004006E, 002CA590): stub > 017c:fixme:imm:ImeSetActiveContext (0x3c780, 0): stub > 017c:fixme:imm:ImmReleaseContext (0000000000020082, 000000000003C780): stub > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:err:richedit:ReadStyleSheet skipping optional destination > 0174:err:richedit:ReadStyleSheet skipping optional destination > 0174:err:richedit:ReadStyleSheet skipping optional destination > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, > advertised shortcut > 0174:fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, > advertised shortcut > 0174:fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, > advertised shortcut > 01e8:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 01f0:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 01e0:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 01f8:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > regsvr32: Successfully registered DLL 'C:\Program Files > (x86)\Rithmic\Rithmic Trader Pro\StockChartX.ocx' > 0174:fixme:msi:internal_ui_handler internal UI not implemented for message > 0x0b000000 (UI level = 5) > 0174:fixme:msi:internal_ui_handler internal UI not implemented for message > 0x0b000000 (UI level = 5) > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0200:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0200:fixme:mscoree:parse_supported_runtime > sku=L".NETFramework,Version=v4.5.2" not implemented > 0200:fixme:mscoree:parse_supported_runtime > sku=L".NETFramework,Version=v4.5.2" not implemented > 0200:fixme:ntdll:NtQuerySystemInformation info_class > SYSTEM_PERFORMANCE_INFORMATION > 0200:fixme:nls:GetFileMUIPath stub: 0x10, > L"C:\\windows\\system32\\tzres.dll", (null), 0032EE98, 00DAA728, 0032EE9C, > 0032EE90 > 0200:fixme:nls:GetFileMUIPath stub: 0x10, > L"C:\\windows\\system32\\tzres.dll", (null), 0032EE98, 00DAA728, 0032EE9C, > 0032EE90 > 0200:fixme:nls:GetFileMUIPath stub: 0x10, > L"C:\\windows\\system32\\tzres.dll", (null), 0032EE98, 00DAA728, 0032EE9C, > 0032EE90 > 0200:fixme:imm:ImeSetActiveContext (0xdc41c0, 1): stub > 0200:fixme:imm:ImmReleaseContext (00030080, 00DC41C0): stub > 0200:fixme:winsock:errno_from_unix unknown error: Device or resource busy > 0200:err:winediag:getaddrinfo Failed to resolve your host name IP > 0218:fixme:wbemprox:wbem_locator_ConnectServer authentication not supported > 0218:fixme:wbemprox:wbem_locator_ConnectServer specific locale not > supported > 0218:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags > 021c:fixme:wbemprox:wbem_locator_ConnectServer authentication not supported > 021c:fixme:wbemprox:wbem_locator_ConnectServer specific locale not > supported > 021c:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags > wine: Read access denied for device L"\\??\\Z:\\", FS volume label and > serial are not available. > 0200:fixme:winsock:errno_from_unix unknown error: Device or resource busy > 0200:err:winediag:getaddrinfo Failed to resolve your host name IP > 0200:fixme:winsock:errno_from_unix unknown error: Device or resource busy > 0200:err:winediag:getaddrinfo Failed to resolve your host name IP > An error occured while contacting the license server. > > Raised in : com.omnesys.omne.om.OMField > Method : OMsetData > Error : no data > Raised in : 31004 1 unknown host 20014 1 unknown addr > > Method : OMaddData > Error : create error > Please contact Omnesys Technologies Inc., at www.omnesys.com. > > On Mon, Sep 12, 2022 at 8:51 AM Jin-oh Kang <jinoh.kang.kr(a)gmail.com> > wrote: > >> On Mon, Sep 12, 2022, 9:46 AM Zebediah Figura <zfigura(a)codeweavers.com> >> wrote: >> >>> On 9/11/22 19:38, Jin-oh Kang wrote: >>> >> and secondly because it's actually quite hard if not >>> >> impossible to implement (POSIX has no way to wait for a mandatory >>> lock, >>> >> for instance). >>> >> >>> > >>> > We don't use POSIX locks to implement file locks; they are emulated >>> > entirely in the server, which I guess is specifically designed to avoid >>> > that problem with POSIX file lock semantics. Thus, this won't be *that* >>> > hard to implement; nonetheless, asynchronous I/O is not really easy to >>> > implement in general, especially for those new to wine codebase. >>> >>> I don't see where you're getting that; we do indeed use POSIX locks. See >>> set_unix_lock() in server/fd.c. >> >> >> I stand corrected. >> >> There's no poll() for file locks, so it would have to busy-wait anyway. >> >> I did incorrectly use the term >>> "mandatory", though; we don't set mandatory locks on a file. >>> >>

1 0

fixing some fixme code
by Owen Hogarth 12 Sep '22

12 Sep '22

Hello, I tried to run an application and saw that there are a few unimplemented features, such as: 00d0:fixme:file:NtLockFile I/O completion on lock not implemented yet I was reading the developers guide and wanted to say hello to the mailing list.

3 4

Wine staging 7.17 release
by Alistair Leslie-Hughes 10 Sep '22

10 Sep '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.17 (529 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Add support for FileFsFullSizeInformation class in NtQueryVolumeInformationFile(try 2) Added: * None Updated: * None Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Ubuntu 20.04 vs 32bit wine [-staging] - more detailed documentation?
by Sebastian M. Ernst 09 Sep '22

09 Sep '22

Hi all, just burned *a lot* of time making Wine (Staging) for 64 and **32 bit** work on Ubuntu 20.04 (Ubuntu 22.04 was a little less painful) as part of a Github action of mine. The official documentation that is very commonly referred / pointed to ("if it does not work, you did not follow the instructions there to the letter") ... https://wiki.winehq.org/Ubuntu ... misses a few, apparently constantly shifting details on the 32 bit side of things. The "authoritative resource" on this topic appears to be this lovely long Github issue ... https://github.com/actions/runner-images/issues/4589 ... which thankfully also provides up-to-date workarounds (with rather significant side-effects), like the following as of July 26: ```bash sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list sudo apt-get update -qq sudo apt-get install -yqq --allow-downgrades libgd3/focal libpcre2-8-0/focal libpcre2-16-0/focal libpcre2-32-0/focal libpcre2-posix2/focal sudo apt-get purge -yqq libmono* moby* mono* php* libgdiplus libpcre2-posix3 libzip4 ``` See, in the following order: - https://github.com/actions/runner-images/issues/4589#issuecomment-980506595 - https://github.com/actions/runner-images/issues/4589#issuecomment-1100899313 - https://github.com/actions/runner-images/issues/4589#issuecomment-1123074635 - https://github.com/actions/runner-images/issues/4589#issuecomment-1194891446 I am not sure if (or how) this belongs into your wiki (of if it can even be fixed / worked around partially within the dependencies of the packages from WineHQ's PPA). But since the above mentioned Github issue is not easy to find between a lot of other related but less helpful "noise" in online search results (and takes a while to comprehend), it might warrant creating a central, well known place that documents this behaviour in an up-to-date manner. Either way, in all honesty, thx to everybody who keeps 32 bit support running. For better or for worse, it is still badly needed. Best regards, Sebastian

3 2

[PATCH] include: disable some process/thread functions when in UAP mode
by Steve Lhomme 08 Sep '22

08 Sep '22

Wine doesn't use the winapifamily.h features but this header is also used in mingw-w64. These functions are also defined in processthreadsapi.h and many of them are not supposed to be called by non desktop apps. In order to have mingw-w64 avoid making these functions public when they should not, winbase.h need to match the mingw-w64 processthreadsapi.h. Either this is fixed in Wine it will need careful update of winbase.h when imported in mingw-w64. --- include/winbase.h | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/include/winbase.h b/include/winbase.h index 0a8409c10e1..f8f04643637 100644 --- a/include/winbase.h +++ b/include/winbase.h @@ -20,6 +20,7 @@ #define __WINE_WINBASE_H #include <winerror.h> +#include <winapifamily.h> #ifdef __cplusplus extern "C" { @@ -1901,15 +1902,19 @@ WINBASEAPI BOOL WINAPI CreateProcessA(LPCSTR,LPSTR,LPSECURITY_ATTRIBUTES, WINBASEAPI BOOL WINAPI CreateProcessW(LPCWSTR,LPWSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION); #define CreateProcess WINELIB_NAME_AW(CreateProcess) WINADVAPI BOOL WINAPI CreateProcessAsUserA(HANDLE,LPCSTR,LPSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCSTR,LPSTARTUPINFOA,LPPROCESS_INFORMATION); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINADVAPI BOOL WINAPI CreateProcessAsUserW(HANDLE,LPCWSTR,LPWSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION); +#endif #define CreateProcessAsUser WINELIB_NAME_AW(CreateProcessAsUser) WINBASEAPI BOOL WINAPI CreateProcessInternalA(HANDLE,LPCSTR,LPSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCSTR,LPSTARTUPINFOA,LPPROCESS_INFORMATION,HANDLE*); WINBASEAPI BOOL WINAPI CreateProcessInternalW(HANDLE,LPCWSTR,LPWSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION,HANDLE*); #define CreateProcessInternal WINELIB_NAME_AW(CreateProcessInternal) WINADVAPI BOOL WINAPI CreateProcessWithLogonW(LPCWSTR,LPCWSTR,LPCWSTR,DWORD,LPCWSTR,LPWSTR,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION); WINADVAPI BOOL WINAPI CreateProcessWithTokenW(HANDLE,DWORD,LPCWSTR,LPWSTR,DWORD,void *,LPCWSTR,STARTUPINFOW *,PROCESS_INFORMATION *); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI HANDLE WINAPI CreateRemoteThread(HANDLE,LPSECURITY_ATTRIBUTES,SIZE_T,LPTHREAD_START_ROUTINE,LPVOID,DWORD,LPDWORD); WINBASEAPI HANDLE WINAPI CreateRemoteThreadEx(HANDLE,LPSECURITY_ATTRIBUTES,SIZE_T,LPTHREAD_START_ROUTINE,LPVOID,DWORD,LPPROC_THREAD_ATTRIBUTE_LIST,LPDWORD); +#endif WINADVAPI BOOL WINAPI CreateRestrictedToken(HANDLE,DWORD,DWORD,PSID_AND_ATTRIBUTES,DWORD,PLUID_AND_ATTRIBUTES,DWORD,PSID_AND_ATTRIBUTES,PHANDLE); WINBASEAPI HANDLE WINAPI CreateSemaphoreA(LPSECURITY_ATTRIBUTES,LONG,LONG,LPCSTR); WINBASEAPI HANDLE WINAPI CreateSemaphoreW(LPSECURITY_ATTRIBUTES,LONG,LONG,LPCWSTR); @@ -1958,7 +1963,9 @@ WINBASEAPI void WINAPI DeleteFiber(LPVOID); WINBASEAPI BOOL WINAPI DeleteFileA(LPCSTR); WINBASEAPI BOOL WINAPI DeleteFileW(LPCWSTR); #define DeleteFile WINELIB_NAME_AW(DeleteFile) +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI void WINAPI DeleteProcThreadAttributeList(struct _PROC_THREAD_ATTRIBUTE_LIST*); +#endif WINBASEAPI BOOL WINAPI DeleteTimerQueue(HANDLE); WINBASEAPI BOOL WINAPI DeleteTimerQueueEx(HANDLE,HANDLE); WINBASEAPI BOOL WINAPI DeleteTimerQueueTimer(HANDLE,HANDLE,HANDLE); @@ -2248,12 +2255,16 @@ WINBASEAPI BOOL WINAPI GetLogicalProcessorInformation(PSYSTEM_LOGICAL_PRO WINBASEAPI BOOL WINAPI GetLogicalProcessorInformationEx(LOGICAL_PROCESSOR_RELATIONSHIP,PSYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX,PDWORD); WINBASEAPI DWORD WINAPI GetProcessHeaps(DWORD,PHANDLE); WINBASEAPI DWORD WINAPI GetProcessId(HANDLE); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI DWORD WINAPI GetProcessIdOfThread(HANDLE); +#endif WINBASEAPI BOOL WINAPI GetProcessIoCounters(HANDLE,PIO_COUNTERS); WINBASEAPI BOOL WINAPI GetProcessPriorityBoost(HANDLE,PBOOL); WINBASEAPI BOOL WINAPI GetProcessShutdownParameters(LPDWORD,LPDWORD); WINBASEAPI BOOL WINAPI GetProcessTimes(HANDLE,LPFILETIME,LPFILETIME,LPFILETIME,LPFILETIME); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI DWORD WINAPI GetProcessVersion(DWORD); +#endif WINBASEAPI BOOL WINAPI GetProcessWorkingSetSize(HANDLE,PSIZE_T,PSIZE_T); WINBASEAPI BOOL WINAPI GetProcessWorkingSetSizeEx(HANDLE,SIZE_T*,SIZE_T*,DWORD*); WINBASEAPI BOOL WINAPI GetProductInfo(DWORD,DWORD,DWORD,DWORD,PDWORD); @@ -2282,7 +2293,9 @@ WINBASEAPI DWORD WINAPI GetShortPathNameA(LPCSTR,LPSTR,DWORD); WINBASEAPI DWORD WINAPI GetShortPathNameW(LPCWSTR,LPWSTR,DWORD); #define GetShortPathName WINELIB_NAME_AW(GetShortPathName) WINBASEAPI VOID WINAPI GetStartupInfoA(LPSTARTUPINFOA); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI VOID WINAPI GetStartupInfoW(LPSTARTUPINFOW); +#endif #define GetStartupInfo WINELIB_NAME_AW(GetStartupInfo) WINBASEAPI HANDLE WINAPI GetStdHandle(DWORD); WINBASEAPI BOOL WINAPI GetSystemCpuSetInformation(SYSTEM_CPU_SET_INFORMATION*,ULONG,ULONG*,HANDLE,ULONG); @@ -2400,7 +2413,9 @@ WINBASEAPI BOOL WINAPI InitializeContext2(void *,DWORD,CONTEXT **,DWORD * WINBASEAPI void WINAPI InitializeCriticalSection(CRITICAL_SECTION *lpCrit); WINBASEAPI BOOL WINAPI InitializeCriticalSectionAndSpinCount(CRITICAL_SECTION *,DWORD); WINBASEAPI BOOL WINAPI InitializeCriticalSectionEx(CRITICAL_SECTION *,DWORD,DWORD); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI InitializeProcThreadAttributeList(struct _PROC_THREAD_ATTRIBUTE_LIST*,DWORD,DWORD,SIZE_T*); +#endif WINADVAPI BOOL WINAPI InitializeSecurityDescriptor(PSECURITY_DESCRIPTOR,DWORD); WINADVAPI BOOL WINAPI InitializeSid(PSID,PSID_IDENTIFIER_AUTHORITY,BYTE); WINBASEAPI VOID WINAPI InitializeSListHead(PSLIST_HEADER); @@ -2559,7 +2574,9 @@ WINBASEAPI VOID WINAPI OutputDebugStringW(LPCWSTR); WINBASEAPI BOOL WINAPI PeekNamedPipe(HANDLE,PVOID,DWORD,PDWORD,PDWORD,PDWORD); WINBASEAPI BOOL WINAPI PostQueuedCompletionStatus(HANDLE,DWORD,ULONG_PTR,LPOVERLAPPED); WINBASEAPI DWORD WINAPI PrepareTape(HANDLE,DWORD,BOOL); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI ProcessIdToSessionId(DWORD,DWORD*); +#endif WINADVAPI BOOL WINAPI PrivilegeCheck(HANDLE,PPRIVILEGE_SET,LPBOOL); WINADVAPI BOOL WINAPI PrivilegedServiceAuditAlarmA(LPCSTR,LPCSTR,HANDLE,PPRIVILEGE_SET,BOOL); WINADVAPI BOOL WINAPI PrivilegedServiceAuditAlarmW(LPCWSTR,LPCWSTR,HANDLE,PPRIVILEGE_SET,BOOL); @@ -2680,7 +2697,9 @@ WINADVAPI BOOL WINAPI SetPrivateObjectSecurity(SECURITY_INFORMATION,PSEC WINADVAPI BOOL WINAPI SetPrivateObjectSecurityEx(SECURITY_INFORMATION,PSECURITY_DESCRIPTOR,PSECURITY_DESCRIPTOR*,ULONG,PGENERIC_MAPPING,HANDLE); WINBASEAPI BOOL WINAPI SetProcessAffinityMask(HANDLE,DWORD_PTR); WINBASEAPI BOOL WINAPI SetProcessPriorityBoost(HANDLE,BOOL); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI SetProcessShutdownParameters(DWORD,DWORD); +#endif WINBASEAPI BOOL WINAPI SetProcessWorkingSetSize(HANDLE,SIZE_T,SIZE_T); WINBASEAPI BOOL WINAPI SetProcessWorkingSetSizeEx(HANDLE,SIZE_T,SIZE_T,DWORD); WINBASEAPI BOOL WINAPI SetSearchPathMode(DWORD); @@ -2698,7 +2717,9 @@ WINBASEAPI BOOL WINAPI SetSystemTimeAdjustment(DWORD,BOOL); WINBASEAPI DWORD WINAPI SetTapeParameters(HANDLE,DWORD,LPVOID); WINBASEAPI DWORD WINAPI SetTapePosition(HANDLE,DWORD,DWORD,DWORD,DWORD,BOOL); WINBASEAPI DWORD_PTR WINAPI SetThreadAffinityMask(HANDLE,DWORD_PTR); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI SetThreadContext(HANDLE,const CONTEXT *); +#endif WINBASEAPI BOOL WINAPI SetThreadErrorMode(DWORD,LPDWORD); WINBASEAPI DWORD WINAPI SetThreadExecutionState(EXECUTION_STATE); WINBASEAPI DWORD WINAPI SetThreadIdealProcessor(HANDLE,DWORD); @@ -2731,7 +2752,9 @@ WINBASEAPI BOOL WINAPI SwitchToThread(void); WINBASEAPI BOOL WINAPI SystemTimeToFileTime(const SYSTEMTIME*,LPFILETIME); WINBASEAPI BOOL WINAPI TerminateJobObject(HANDLE,UINT); WINBASEAPI BOOL WINAPI TerminateProcess(HANDLE,DWORD); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI TerminateThread(HANDLE,DWORD); +#endif WINBASEAPI DWORD WINAPI TlsAlloc(void); WINBASEAPI BOOL WINAPI TlsFree(DWORD); WINBASEAPI LPVOID WINAPI TlsGetValue(DWORD); @@ -2753,7 +2776,9 @@ WINBASEAPI BOOL WINAPI UmsThreadYield(void *); WINBASEAPI HRESULT WINAPI UnregisterApplicationRestart(void); WINBASEAPI BOOL WINAPI UnregisterWait(HANDLE); WINBASEAPI BOOL WINAPI UnregisterWaitEx(HANDLE,HANDLE); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI UpdateProcThreadAttribute(struct _PROC_THREAD_ATTRIBUTE_LIST*,DWORD,DWORD_PTR,void*,SIZE_T,void*,SIZE_T*); +#endif WINBASEAPI BOOL WINAPI UpdateResourceA(HANDLE,LPCSTR,LPCSTR,WORD,LPVOID,DWORD); WINBASEAPI BOOL WINAPI UpdateResourceW(HANDLE,LPCWSTR,LPCWSTR,WORD,LPVOID,DWORD); #define UpdateResource WINELIB_NAME_AW(UpdateResource) -- 2.29.2

3 3

[PATCH] ntdll: Complete error case in get_initial_environment
by Gerald Pfeifer 06 Sep '22

06 Sep '22

GCC 12 (rightfully) would warn dlls/ntdll/unix/env.c:1910:12: warning: 'env_pos' may be used uninitialized Signed-off-by: Gerald Pfeifer <gerald(a)pfeifer.com> --- dlls/ntdll/unix/env.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/dlls/ntdll/unix/env.c b/dlls/ntdll/unix/env.c index 105038a34cb..cbbfb99f4b3 100644 --- a/dlls/ntdll/unix/env.c +++ b/dlls/ntdll/unix/env.c @@ -920,7 +920,11 @@ static WCHAR *get_initial_environment( SIZE_T *pos, SIZE_T *size ) *size = 1; for (e = main_envp; *e; e++) *size += strlen(*e) + 1; - if (!(env = malloc( *size * sizeof(WCHAR) ))) return NULL; + if (!(env = malloc( *size * sizeof(WCHAR) ))) + { + *pos = 0; + return NULL; + } ptr = env; end = env + *size - 1; for (e = main_envp; *e && ptr < end; e++) -- 2.34.1

2 1

RFC: Allow marking unreliable tests as flaky.
by Francois Gouget 02 Sep '22

02 Sep '22

Wine has many unreliable tests which makes it hard to know whether a patch causes new failures. So one proposal was to mark unreliable tests as flaky, and have a mode where flaky failures can ignored by setting $WINETEST_ALLOW_FLAKY. So one would be able to apply a patch, run 'WINETEST_ALLOW_FLAKY=1 make test' and if that fails that means the patch introduces a new failure. The way it works is that when a flaky test fails the message is 'Flaky failed...' instead of 'Test failed...'. I also added the count of flaky failures to the summary line. So the flaky failures are not totally swept under the rug. The main difference is that if $WINETEST_ALLOW_FLAKY is set, the exit code is 0 if the only failures are flaky ones. That still leaves some open questions though: * Should the message be 'Test failed' instead of 'Flaky failed' when $WINETEST_ALLOW_FLAKY is not set? I opted for the latter because it adds information that the failed test has been marked as flaky. * Should tests that fail systematically on some platforms but not others (for instance specific Windows versions, specific locales, specific GPUs) be marked as flaky? Or should flaky be reserved for tests that fail randomly? * What about failures where the message is different every time so that the failure always looks new? Should these not be marked as flaky since it only impacts the TestBot? * On a related note the patch below has flaky_windows and flaky_wine macros. Is that too fine grained? Maybe we don't want to run the risk of marking a test as flaky_windows only to discover later that it can also fail in Wine? But conversely, wouldn't it be valuable to know that a test is only flaky in Wine and not in Windows? Note: flaky_windows is a bit long but I was worried that flaky_win would be too similar to flaky_wine. * I decided having flaky_{windows,wine}_if() macros would be overkill. * How does one know a flaky directive can be removed? * Is it allowed to submit a patch that contains new flaky directives? * Also the flaky directive cannot deal with tests that randomly crash, prematurely exit, or time out. These issues are rarer so maybe we can hope they can all be fixed? * How does this impact bug 48912, aka "Allow blacklisting unreliable and always new failures"? https://bugs.winehq.org/show_bug.cgi?id=48912 * test.winehq.org and the TestBot will need to be updated to highlight the new messages and, more importantly, to recognize the new summary line. The patch is below and I bundled it with tweaks to a few tests for illustration purposes: d3d8:device - Failure happens on Windows (rarely) and Wine. dinput:mouse - Failure happens on Windows 7 and Wine. mmdevapi:render - Timing issue. schedsvc:atsvcapi - Wine-only failure. --- dlls/d3d8/tests/device.c | 2 +- dlls/dinput/tests/mouse.c | 2 +- dlls/mmdevapi/tests/render.c | 2 +- dlls/schedsvc/tests/atsvcapi.c | 2 +- include/wine/test.h | 78 +++++++++++++++++++++++++++++----- 5 files changed, 72 insertions(+), 14 deletions(-) diff --git a/dlls/d3d8/tests/device.c b/dlls/d3d8/tests/device.c index cb1e83b64b3..f0e8c27fafd 100644 --- a/dlls/d3d8/tests/device.c +++ b/dlls/d3d8/tests/device.c @@ -3356,7 +3356,7 @@ static void test_wndproc(void) expect_messages = sc_maximize_messages; SendMessageA(focus_window, WM_SYSCOMMAND, SC_MAXIMIZE, 0); - ok(!expect_messages->message, "Expected message %#x for window %#x, but didn't receive it.\n", + flaky ok(!expect_messages->message, "Expected message %#x for window %#x, but didn't receive it.\n", expect_messages->message, expect_messages->window); expect_messages = NULL; flush_events(); diff --git a/dlls/dinput/tests/mouse.c b/dlls/dinput/tests/mouse.c index 8be808e5da6..dcb5453a825 100644 --- a/dlls/dinput/tests/mouse.c +++ b/dlls/dinput/tests/mouse.c @@ -156,7 +156,7 @@ static void test_acquire(IDirectInputA *pDI, HWND hwnd) SetActiveWindow( hwnd ); hr = IDirectInputDevice_Acquire(pMouse); - ok(hr == S_OK, "Acquire() failed: %#lx\n", hr); + flaky ok(hr == S_OK, "Acquire() failed: %#lx\n", hr); mouse_event(MOUSEEVENTF_MOVE, 10, 10, 0, 0); cnt = 1; diff --git a/dlls/mmdevapi/tests/render.c b/dlls/mmdevapi/tests/render.c index 4e19b91c5f5..882be89b7ff 100644 --- a/dlls/mmdevapi/tests/render.c +++ b/dlls/mmdevapi/tests/render.c @@ -1098,7 +1098,7 @@ static void test_clock(int share) ok(pos == 0, "GetPosition returned non-zero pos before being started\n"); hr = IAudioClient_Start(ac); /* #1 */ - ok(hr == S_OK, "Start failed: %08lx\n", hr); + flaky ok(hr == S_OK, "Start failed: %08lx\n", hr); Sleep(100); slept += 100; diff --git a/dlls/schedsvc/tests/atsvcapi.c b/dlls/schedsvc/tests/atsvcapi.c index 3aaad8b5cfe..83774804b40 100644 --- a/dlls/schedsvc/tests/atsvcapi.c +++ b/dlls/schedsvc/tests/atsvcapi.c @@ -168,7 +168,7 @@ START_TEST(atsvcapi) skip_tests_delete: ret = NetrJobDel(server_name, jobid, jobid); - ok(ret == ERROR_SUCCESS, "NetrJobDel error %lu\n", ret); + flaky_wine ok(ret == ERROR_SUCCESS, "NetrJobDel error %lu\n", ret); skip_tests: SetUnhandledExceptionFilter(old_exception_filter); diff --git a/include/wine/test.h b/include/wine/test.h index 01ba81f4857..422ba3dce38 100644 --- a/include/wine/test.h +++ b/include/wine/test.h @@ -50,6 +50,9 @@ extern int winetest_time; /* running in interactive mode? */ extern int winetest_interactive; +/* always count flaky tests as successful (BOOL) */ +extern int winetest_allow_flaky; + /* report successful tests (BOOL) */ extern int winetest_report_success; @@ -117,6 +120,13 @@ extern void winetest_pop_context(void); #define trace trace_(__FILE__, __LINE__) #define wait_child_process wait_child_process_(__FILE__, __LINE__) +#define flaky_if(is_flaky) for (winetest_start_flaky(is_flaky); \ + winetest_loop_flaky(); \ + winetest_end_flaky()) +#define flaky flaky_if(1) +#define flaky_windows flaky_if(!strcmp(winetest_platform, "windows")) +#define flaky_wine flaky_if(!strcmp(winetest_platform, "wine")) + #define todo_if(is_todo) for (winetest_start_todo(is_todo); \ winetest_loop_todo(); \ winetest_end_todo()) @@ -200,6 +210,9 @@ int winetest_interactive = 0; /* current platform */ const char *winetest_platform = "windows"; +/* always count flaky tests as successful (BOOL) */ +int winetest_allow_flaky; + /* report successful tests (BOOL) */ int winetest_report_success = 0; @@ -214,6 +227,7 @@ static const struct test *current_test; /* test currently being run */ static LONG successes; /* number of successful tests */ static LONG failures; /* number of failures */ +static LONG flaky_failures; /* number of failures inside flaky block */ static LONG skipped; /* number of skipped test chunks */ static LONG todo_successes; /* number of successful tests inside todo block */ static LONG todo_failures; /* number of failures inside todo block */ @@ -229,6 +243,8 @@ struct tls_data { const char* current_file; /* file of current check */ int current_line; /* line of current check */ + unsigned int flaky_level; /* current flaky nesting level */ + int flaky_do_loop; unsigned int todo_level; /* current todo nesting level */ int todo_do_loop; char *str_pos; /* position in debug buffer */ @@ -355,9 +371,18 @@ int winetest_vok( int condition, const char *msg, va_list args ) { if (condition) { - winetest_print_context( "Test succeeded inside todo block: " ); - vprintf(msg, args); - InterlockedIncrement(&todo_failures); + if (data->flaky_level) + { + winetest_print_context( "Flaky succeeded inside todo block: " ); + vprintf(msg, args); + InterlockedIncrement(&flaky_failures); + } + else + { + winetest_print_context( "Test succeeded inside todo block: " ); + vprintf(msg, args); + InterlockedIncrement(&todo_failures); + } return 0; } else @@ -381,9 +406,18 @@ int winetest_vok( int condition, const char *msg, va_list args ) { if (!condition) { - winetest_print_context( "Test failed: " ); - vprintf(msg, args); - InterlockedIncrement(&failures); + if (data->flaky_level) + { + winetest_print_context( "Flaky failed: " ); + vprintf(msg, args); + InterlockedIncrement(&flaky_failures); + } + else + { + winetest_print_context( "Test failed: " ); + vprintf(msg, args); + InterlockedIncrement(&failures); + } return 0; } else @@ -456,6 +490,27 @@ void winetest_win_skip( const char *msg, ... ) va_end(valist); } +void winetest_start_flaky( int is_flaky ) +{ + struct tls_data *data = get_tls_data(); + data->flaky_level = (data->flaky_level << 1) | (is_flaky != 0); + data->flaky_do_loop=1; +} + +int winetest_loop_flaky(void) +{ + struct tls_data *data = get_tls_data(); + int do_flaky=data->flaky_do_loop; + data->flaky_do_loop=0; + return do_flaky; +} + +void winetest_end_flaky(void) +{ + struct tls_data *data = get_tls_data(); + data->flaky_level >>= 1; +} + void winetest_start_todo( int is_todo ) { struct tls_data *data = get_tls_data(); @@ -601,14 +656,16 @@ static int run_test( const char *name ) printf( "%04x:%s:%s Silenced %d todos, %d skips and %d traces.\n", (UINT)GetCurrentProcessId(), test->name, winetest_elapsed(), (UINT)muted_todo_successes, (UINT)muted_skipped, (UINT)muted_traces); - printf( "%04x:%s:%s %d tests executed (%d marked as todo, %d %s), %d skipped.\n", + printf( "%04x:%s:%s %d tests executed (%d marked as todo, %d as flaky, %d %s), %d skipped.\n", (UINT)GetCurrentProcessId(), test->name, winetest_elapsed(), - (UINT)(successes + failures + todo_successes + todo_failures), - (UINT)todo_successes, (UINT)(failures + todo_failures), + (UINT)(successes + failures + flaky_failures + todo_successes + todo_failures), + (UINT)todo_successes, (UINT)flaky_failures, (UINT)(failures + todo_failures), (failures + todo_failures != 1) ? "failures" : "failure", (UINT)skipped ); } - status = (failures + todo_failures < 255) ? failures + todo_failures : 255; + status = failures + todo_failures; + if (!winetest_allow_flaky) status += flaky_failures; + if (status > 255) status = 255; return status; } @@ -665,6 +722,7 @@ int main( int argc, char **argv ) if (GetEnvironmentVariableA( "WINETEST_DEBUG", p, sizeof(p) )) winetest_debug = atoi(p); if (GetEnvironmentVariableA( "WINETEST_INTERACTIVE", p, sizeof(p) )) winetest_interactive = atoi(p); + if (GetEnvironmentVariableA( "WINETEST_ALLOW_FLAKY", p, sizeof(p) )) winetest_allow_flaky = atoi(p); if (GetEnvironmentVariableA( "WINETEST_REPORT_SUCCESS", p, sizeof(p) )) winetest_report_success = atoi(p); if (GetEnvironmentVariableA( "WINETEST_TIME", p, sizeof(p) )) winetest_time = atoi(p); winetest_last_time = winetest_start_time = GetTickCount(); -- 2.30.2

7 12

Puzzling IPrincipal:UserId check in taskschd
by Francois Gouget 31 Aug '22

31 Aug '22

So I'm a bit puzzled by this check in taskschd/task.c's write_principal(): hr = IPrincipal_get_UserId(principal, &bstr); if (hr == S_OK && lstrlenW(bstr)) { hr = write_text_value(stream, L"UserId", bstr); What's puzzling to me is the lstrlenW(bstr) check: * write_principal() has no such check for Id, GroupId, DisplayName and RunLevel. Maybe that's because they are guaranteed to be set and non empty but I could not find any documentation saying so and they are not implemented in Wine. * write_registration_info() is very similar but checks bstr, not what is in effect *bstr: hr = IRegistrationInfo_get_Source(reginfo, &bstr); if (hr == S_OK && bstr) { hr = write_text_value(stream, L"Source", bstr); * We don't seem to have tests showing how this works. I would expect all these property getters to work the same way. So would something like that make more sense? hr = IPrincipal_get_UserId(principal, &bstr); if (hr == S_OK && bstr) { hr = write_text_value(stream, L"UserId", bstr); Dmitry: Do you remember if you wrote the lstrlenW(bstr) check because of some test you did? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Computers are like airconditioners They stop working properly if you open WINDOWS

2 1

Whenever i use wine this message pop up and the application doesn't run please any help
by anthonyuser33 29 Aug '22

29 Aug '22

Sent from my Galaxy

1 0

Wine staging 7.16 release
by Alistair Leslie-Hughes 29 Aug '22

29 Aug '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.16 (531 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * wined3d: Use wined3d_array_reserve() in wined3d_adapter_create_output(). * dsdmo: Add Echo FX Support * dsdmo: Add Compressor FX Support * ddraw: Don't set HWTRANSFORMANDLIGHT flag on d3d7 RGB device. Added: * None Updated: * none Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

[PATCH 1/2] readme: Update Finnish translation.
by Lauri Kenttä 29 Aug '22

29 Aug '22

Signed-off-by: Lauri Kenttä <lauri.kentta(a)gmail.com> --- documentation/README.fi | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/documentation/README.fi b/documentation/README.fi index e459bbc779a..00af959c033 100644 --- a/documentation/README.fi +++ b/documentation/README.fi @@ -146,6 +146,8 @@ Kysymyksiä: Wiki: Wine Wiki on osoitteessa https://wiki.winehq.org/. +Gitlab: Winen kehitykseen voi osallistua sivustolla https://gitlab.winehq.org + Postituslistat: Winen käyttäjille ja kehittäjille on joitakin postituslistoja, sivulla https://www.winehq.org/forums kerrotaan niistä lisää. @@ -157,14 +159,6 @@ Virheet: IRC: Online-apua voi saada kanavalta #WineHQ palvelimella irc.libera.chat. -Git: Winen tämänhetkinen kehitysversio on jaossa Git-järjestelmän kautta. - Sivulla https://www.winehq.org/git kerrotaan tästä lisää. - - -Jos lisäät jotain tai korjaat jonkin virheen, lähetä toki muutoksesi -(mieluiten komennon git-format-patch avulla) listalle wine-devel(a)winehq.org, -jotta se voidaan lisätä Winen seuraavaan versioon. - -- Alkuperäisen version tekstistä on kirjoittanut Alexandre Julliard -- 2.37.2

2 2

Upcoming vkd3d 1.5 release.
by Henri Verbeet 24 Aug '22

24 Aug '22

Hi all, As previously discussed, we'd like to release vkd3d 1.5 in about 4 weeks. Practically speaking, that means that as we're nearing that date, the vkd3d tree is going to become progressively frozen, starting today. Now is the time to test your games for any regressions, review any API changes since vkd3d 1.4, review/improve the API documentation, and so on. If you're working on any larger features or architectural changes, ideally you'd have those ready to merge shortly after the 1.5 release, so that they'll make it into the 1.6 release, tentatively planned for early December. Regards, Henri

1 0

wine-devel moved to Mailman3
by Jeremy Newman 22 Aug '22

22 Aug '22

This list has been migrated to a new interface. To manage your subscription go here: https://www.winehq.org/mailman3/postorius/lists/wine-devel.winehq.org/ To view the archives go here: https://www.winehq.org/mailman3/hyperkitty/list/wine-devel@winehq.org/ The old archives will remain online to preserve links. -N

1 0

[PATCH 1/2] user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.
by Dmitry Timoshkov 18 Aug '22

18 Aug '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/user32/tests/sysparams.c | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/dlls/user32/tests/sysparams.c b/dlls/user32/tests/sysparams.c index 4f2709094e9..e354ef69a94 100644 --- a/dlls/user32/tests/sysparams.c +++ b/dlls/user32/tests/sysparams.c @@ -4124,6 +4124,31 @@ static void test_GetAutoRotationState(void) ok(ret, "Expected GetAutoRotationState to succeed, error %ld\n", GetLastError()); } +static void test_LOGFONT_charset(void) +{ + CHARSETINFO csi; + LOGFONTA lf; + NONCLIENTMETRICSA ncm; + BOOL ret; + + ret = TranslateCharsetInfo(ULongToPtr(GetACP()), &csi, TCI_SRCCODEPAGE); + ok(ret, "TranslateCharsetInfo(%d) error %lu\n", GetACP(), GetLastError()); + + GetObjectA(GetStockObject(DEFAULT_GUI_FONT), sizeof(lf), &lf); + ok(lf.lfCharSet == csi.ciCharset, "got %d, expected %d\n", lf.lfCharSet, csi.ciCharset); + + ret = SystemParametersInfoA(SPI_GETICONTITLELOGFONT, sizeof(lf), &lf, FALSE); + ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); + todo_wine + ok(lf.lfCharSet == DEFAULT_CHARSET, "got %d\n", lf.lfCharSet); + + ncm.cbSize = FIELD_OFFSET(NONCLIENTMETRICSA, iPaddedBorderWidth); + ret = SystemParametersInfoA(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0); + ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); + todo_wine + ok(ncm.lfCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfCaptionFont.lfCharSet); +} + START_TEST(sysparams) { int argc; @@ -4172,6 +4197,8 @@ START_TEST(sysparams) strict=(argc >= 3 && strcmp(argv[2],"strict")==0); trace("strict=%d\n",strict); + test_LOGFONT_charset(); + trace("testing GetSystemMetrics with your current desktop settings\n"); test_GetSystemMetrics( ); test_metrics_for_dpi( 192 ); -- 2.37.2

2 2

[PATCH 2/2] user32: Set font charset to DEFAULT_CHARSET to support locale change.
by Dmitry Timoshkov 18 Aug '22

18 Aug '22

Otherwise when the prefix was created with one locale and later an application in the prefix is running with a different locale values cached in the registry lead to broken UI. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/user32/tests/sysparams.c | 4 ++-- dlls/win32u/sysparams.c | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/dlls/user32/tests/sysparams.c b/dlls/user32/tests/sysparams.c index e354ef69a94..6ab7010c4ed 100644 --- a/dlls/user32/tests/sysparams.c +++ b/dlls/user32/tests/sysparams.c @@ -4139,14 +4139,13 @@ static void test_LOGFONT_charset(void) ret = SystemParametersInfoA(SPI_GETICONTITLELOGFONT, sizeof(lf), &lf, FALSE); ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); - todo_wine ok(lf.lfCharSet == DEFAULT_CHARSET, "got %d\n", lf.lfCharSet); ncm.cbSize = FIELD_OFFSET(NONCLIENTMETRICSA, iPaddedBorderWidth); ret = SystemParametersInfoA(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0); ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); - todo_wine ok(ncm.lfCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfCaptionFont.lfCharSet); + ok(ncm.lfSmCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfSmCaptionFont.lfCharSet); } START_TEST(sysparams) diff --git a/dlls/win32u/sysparams.c b/dlls/win32u/sysparams.c index 52665f7a641..879dffb58e2 100644 --- a/dlls/win32u/sysparams.c +++ b/dlls/win32u/sysparams.c @@ -3039,12 +3039,14 @@ static BOOL get_font_entry( union sysparam_all_entry *entry, UINT int_param, voi switch (load_entry( &entry->hdr, &font, sizeof(font) )) { case sizeof(font): + font.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ if (font.lfHeight > 0) /* positive height value means points ( inch/72 ) */ font.lfHeight = -muldiv( font.lfHeight, USER_DEFAULT_SCREEN_DPI, 72 ); entry->font.val = font; break; case sizeof(LOGFONT16): /* win9x-winME format */ logfont16to32( (LOGFONT16 *)&font, &entry->font.val ); + entry->font.val.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ if (entry->font.val.lfHeight > 0) entry->font.val.lfHeight = -muldiv( entry->font.val.lfHeight, USER_DEFAULT_SCREEN_DPI, 72 ); break; @@ -3055,6 +3057,7 @@ static BOOL get_font_entry( union sysparam_all_entry *entry, UINT int_param, voi /* fall through */ case 0: /* use the default GUI font */ NtGdiExtGetObjectW( GetStockObject( DEFAULT_GUI_FONT ), sizeof(font), &font ); + font.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ font.lfHeight = map_from_system_dpi( font.lfHeight ); font.lfWeight = entry->font.weight; entry->font.val = font; @@ -3094,6 +3097,7 @@ static BOOL set_font_entry( union sysparam_all_entry *entry, UINT int_param, voi static BOOL init_font_entry( union sysparam_all_entry *entry ) { NtGdiExtGetObjectW( GetStockObject( DEFAULT_GUI_FONT ), sizeof(entry->font.val), &entry->font.val ); + entry->font.val.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ entry->font.val.lfHeight = map_from_system_dpi( entry->font.val.lfHeight ); entry->font.val.lfWeight = entry->font.weight; get_real_fontname( &entry->font.val, entry->font.fullname ); -- 2.37.2

1 0

wine-cvs renamed to wine-commits
by Jeremy Newman 17 Aug '22

17 Aug '22

The wine-cvs mailing list for git push notifications has *finally* been renamed to wine-commits. How many years has it been since we switched away from cvs? Something like 15 years! We also migrated the list over to mailman v3 so the links to the archives and subscription management have changed. The old archives will remain online to not break links. All the lists save one have been migrated. We will be migrating wine-devel soonish(tm). Updated links to the mailing lists and archives are here: https://www.winehq.org/forums Remember to update your email filters. -N

1 0

Patch tracker
by Alexandre Julliard 16 Aug '22

16 Aug '22

Folks, We now have an automated reviewer assignment bot in Gitlab, thanks to the work of Jeremy White, so I think it's time to retire the wine-devel patch tracker. From now on, please submit everything through merge requests; patches sent to wine-devel will no longer be applied. Some reminders about the new policies: - Adding a Signed-off-by header is no longer necessary. This is replaced by the Gitlab approval mechanism. - When a new MR is submitted, the bot will assign reviewers based on the MAINTAINERS file. If the bot got it wrong, or if you would like to request reviews from other people, feel free to modify the list of reviewers. - If you don't have permission to modify reviewers, you should request access to the Wine project. There should be a link for this on the main project page at https://gitlab.winehq.org/wine/wine - I won't merge a MR until all reviewers have approved it. If you are assigned as reviewer but are unable/unwilling to review that MR, please unassign yourself so that the MR isn't blocked waiting for your approval. - In general, approving your own MR is not necessary or useful. - As an exception to the above, if your MR contains commits authored by someone else, you are asked to explicitly approve it. The bot will assign you as an extra reviewer in that case. - Approval information is stored in git notes. You can fetch the refs/notes/commits head if you'd like to see that information in your local tree. - We now have a CI pipeline to make sure that all the commits of a MR compile cleanly. Later on, the pipeline will also run the tests. Make sure to check the pipeline results; a MR with a failed pipeline won't be merged. Questions? Comments? -- Alexandre Julliard julliard(a)winehq.org

4 7

[PATCH] qedit: Remove "ugly" work around
by Brendan McGrath 15 Aug '22

15 Aug '22

This patch removes a work around that causes a crash in Unravel Two. There is a callback in Unravel Two that appears to add a reference to a IMediaSample, which this work around treats as a leak and releases. However, the application also releases the reference causing a negative overflow and an assertion failure on line 345 of dlls/quartz/memallocator.c. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51616 Signed-off-by: Brendan McGrath <brendan(a)redmandi.com> --- Although I'm not convinced just deleting 12 yr old code is a great idea, the original author did describe this work around as "ugly". I would describe it as unsafe. See Wine Bug 51616. I think it may also be possible for the work around to fail in a multi-threaded scenario, where the IMediaSample is accessed in parallel to the callback; potentially with a negative overflow of its own (and looping 4294967295 times). Although I'm not familiar enough with the uses of qedit to understand if this is even plausible. Unfortunately, I've only tested the removal of this work around with the one application; Unravel Two. Also note that I've only been able to test this "fix" with a local build of Proton 7 Experimental. I couldn't get the application to run in vanilla Wine (as the Origin launcher failed to install). Definitely interested in thoughts. dlls/qedit/samplegrabber.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/dlls/qedit/samplegrabber.c b/dlls/qedit/samplegrabber.c index 9b9780e564a8..cefb2f370785 100644 --- a/dlls/qedit/samplegrabber.c +++ b/dlls/qedit/samplegrabber.c @@ -164,9 +164,6 @@ static void SampleGrabber_callback(struct sample_grabber *This, IMediaSample *sa if (ref) { ERR("(%p) Callback referenced sample %p by %lu\n", This, sample, ref); - /* ugly as hell but some apps are sooo buggy */ - while (ref--) - IMediaSample_Release(sample); } } break; -- 2.34.1

4 6

Wine staging 7.15 release
by Alistair Leslie-Hughes 14 Aug '22

14 Aug '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.15 (536 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * xactengine3_7: Record context for each notification. * xactengine3_7: Add helper function to add entries. * xactengine3_7: Map SoundBank interfaces. * xactengine3_7: Map IXACT3Cue interfaces. * xactengine3_7: Map IXACT3Wave interfaces. * xactengine3_7: Implement callback for supported messages. Added: * [52396] ntdll: Don't use Wine frames during exception processing on x64. * [52396] dsdmo: Add more FX interfaces. * [53497] wined3d: Use wined3d_array_reserve() in wined3d_adapter_create_output() Updated: * none Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: [PATCH v2 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.
by Marvin 12 Aug '22

12 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121155 Your paranoid android. === w1064 (32 bit report) === d3d11: d3d11.c:5914: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:28519: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28528: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28519: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28519: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28528: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28528: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH v2 2/3] d3d11: Always return E_FAIL for formats which have no support flags.
by Marvin 12 Aug '22

12 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121154 Your paranoid android. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Test marked todo: Feature level 0xb000: Format 0x5b - display not supported, format support 0x80f3f1. d3d11.c:1571: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: d3d11.c:1576: Test marked todo: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:9946: Test failed: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:28489: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28498: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28489: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28489: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28498: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28498: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH v2 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.
by Marvin 12 Aug '22

12 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121153 Your paranoid android. === w10pro64 (32 bit report) === d3d11: d3d11.c:5914: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:28486: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28486: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28486: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.
by Marvin 11 Aug '22

11 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121056 Your paranoid android. === w1064_adm (64 bit report) === d3d11: d3d11.c:5910: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28515: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28515: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28524: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28524: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:28515: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28524: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28278: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28278: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28278: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28286: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28286: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28295: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 2/3] d3d11: Always return E_FAIL for formats which have no support flags.
by Marvin 11 Aug '22

11 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121055 Your paranoid android. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28485: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28485: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28494: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28494: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28485: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28494: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28248: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28248: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28248: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28256: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28256: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28265: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.
by Marvin 11 Aug '22

11 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121054 Your paranoid android. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28482: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28491: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28482: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28482: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28491: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28491: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28428: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:28428: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28428: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28245: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28245: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28245: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28253: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28253: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28262: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 1/6] mshtml: Forward Document's Invoke to InvokeEx.
by Marvin 11 Aug '22

11 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121042 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

WineConf 2022 - Bring out your talks
by Jeremy White 11 Aug '22

11 Aug '22

Hey folks, I've just learned that what we've done all these years is an un conference (https://en.wikipedia.org/wiki/Unconference) or a BarCamp (https://en.wikipedia.org/wiki/BarCamp). So we were cool *long* before these other cats starting copying us. However, since we are partnering with X.org on Wine Conf, and they use the slick Indico conference system, we should get with the program. I would really appreciate it if folks could submit talk ideas: https://indico.freedesktop.org/event/2/abstracts/ We have, a non zero number of scheduled presentations already, but think that number may be one. So I would really appreciate it if folks would submit abstracts. Cheers, Jeremy p.s. Other reminders: - We have funds available to sponsor travel. If cost makes you hesitate, please reach out to me privately. - There is a hotel block you can sign up for - New this year, it's nice if you sign to show you are coming: https://indico.freedesktop.org/event/2/registrations/2/.

2 1

Re: [PATCH v2 4/6] mf: Allow resolving topology with missing downstream current type.
by Marvin 11 Aug '22

11 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121023 Your paranoid android. === w10pro64_ja (64 bit report) === mf: mf: Timeout

1 0

Re: [PATCH 1/5] comctl32/tests: Add IME tests for edit control.
by Marvin 11 Aug '22

11 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120932 Your paranoid android. === w10pro64 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v3 1/2] mshtml: Semi-implement non-string primitive data for postMessage.
by Marvin 10 Aug '22

10 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120888 Your paranoid android. === w10pro64_zh_CN (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH v5 01/10] winmm/tests: Add tests for visibility of video window.
by Marvin 10 Aug '22

10 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120860 Your paranoid android. === w7u_adm (32 bit report) === winmm: midi.c:988: Test failed: bad message 1e/0 from midiStreamOpen, expect 3c7/0 midi.c:1039: Test failed: bad message 3c7/0 from midiStreamOut, expect 3c9/22f940 midi.c:1048: Test failed: bad message 3c9/22f940 from midiStreamClose, expect 3c8/0 === w7u_adm (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w7u_adm (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v4 03/13] mmdevapi: Integrate winepulse's additions in unixlib.h
by Marvin 10 Aug '22

10 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120814 Your paranoid android. === debian11 (32 bit Chinese:China report) === mmdevapi: capture.c:205: Test failed: GCP 16553 past ReleaseBuffer(0) initially 16058

1 0

Re: [PATCH 1/1] d3d11: Validate layout description in d3d_input_layout_create().
by Marvin 09 Aug '22

09 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120787 Your paranoid android. === w1064 (32 bit report) === d3d11: d3d11.c:5908: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: d3d11.c:1570: Test marked todo: Format 0x57 - display not supported, feature_level 0x9200, format support 0x200f3f2.

1 0

Re: [PATCH v2 1/2] mshtml: Semi-implement non-string primitive data for postMessage.
by Marvin 09 Aug '22

09 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120782 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

WinRt activable class registration
by Kacper rączy 09 Aug '22

09 Aug '22

Hi everyone, First of all, I’m not really familiar with Windows dev environment and tools outside of wine. I’m building custom implementation of some Windows Runtime modules (separate project outside of wine-tree). Similarly to windows.gaming.input in wine, I’ve created classes.idl with `#pragma makedep register`, and using widl to compile it into classes_r.res script file. Then I’m using windres to convert to coff and link it against my dll. Then the runtime classes implemented by dll have to registered. So far I was adding registry entries with DllPath manually in regedit (in HKLM.Software.Microsoft.WindowsRuntime.ActivatableClassId.[CLASS_NAME]) for testing purposes, because I don’t really know how utilize registration script that’s already embedded in dll. So my question is, how do I register Dll for activable winrt classes? Is there a tool for that? Thanks, Kacper Rączy

1 0

Re: [PATCH 2/2] ntdll: Fix leak of mach_host_self port.
by Marvin 08 Aug '22

08 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120698 Your paranoid android. === debian11 (32 bit WoW report) === ntdll: change.c:277: Test failed: should be ready

1 0

Re: [PATCH v2 1/2] mf: Handle timer time behind clock time in present_clock_schedule_timer().
by Marvin 08 Aug '22

08 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120690 Your paranoid android. === w7u_el (32 bit report) === mf: mf: Timeout

1 0

[PATCH] srvsvc: Add LanmanServer stub service.
by Dmitry Timoshkov 08 Aug '22

08 Aug '22

wine.inf already has an entry for it. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- configure.ac | 1 + dlls/srvsvc/Makefile.in | 5 +++ dlls/srvsvc/srvsvc.c | 87 +++++++++++++++++++++++++++++++++++++++++ dlls/srvsvc/srvsvc.spec | 1 + loader/wine.inf.in | 4 +- 5 files changed, 96 insertions(+), 2 deletions(-) create mode 100644 dlls/srvsvc/Makefile.in create mode 100644 dlls/srvsvc/srvsvc.c create mode 100644 dlls/srvsvc/srvsvc.spec diff --git a/configure.ac b/configure.ac index dd4abd39e32..bec0513c46d 100644 --- a/configure.ac +++ b/configure.ac @@ -3035,6 +3035,7 @@ WINE_CONFIG_MAKEFILE(dlls/spoolss/tests) WINE_CONFIG_MAKEFILE(dlls/sppc) WINE_CONFIG_MAKEFILE(dlls/srclient) WINE_CONFIG_MAKEFILE(dlls/srvcli) +WINE_CONFIG_MAKEFILE(dlls/srvsvc) WINE_CONFIG_MAKEFILE(dlls/sspicli) WINE_CONFIG_MAKEFILE(dlls/stdole2.tlb) WINE_CONFIG_MAKEFILE(dlls/stdole32.tlb) diff --git a/dlls/srvsvc/Makefile.in b/dlls/srvsvc/Makefile.in new file mode 100644 index 00000000000..f9c68fd12aa --- /dev/null +++ b/dlls/srvsvc/Makefile.in @@ -0,0 +1,5 @@ +MODULE = srvsvc.dll +IMPORTS = advapi32 + +C_SRCS = \ + srvsvc.c diff --git a/dlls/srvsvc/srvsvc.c b/dlls/srvsvc/srvsvc.c new file mode 100644 index 00000000000..3b2b563bc6c --- /dev/null +++ b/dlls/srvsvc/srvsvc.c @@ -0,0 +1,87 @@ +/* + * LanmanServer Service + * + * Copyright 2022 Dmitry Timoshkov + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA + */ + +#include <stdarg.h> + +#include "windef.h" +#include "winbase.h" +#include "winsvc.h" +#include "wine/debug.h" + +WINE_DEFAULT_DEBUG_CHANNEL(lanman); + +static SERVICE_STATUS_HANDLE svc_handle; +static HANDLE done_event; + +static void svc_update_status(DWORD state) +{ + SERVICE_STATUS status; + + status.dwServiceType = SERVICE_WIN32; + status.dwControlsAccepted = SERVICE_ACCEPT_STOP | SERVICE_ACCEPT_SHUTDOWN; + status.dwWin32ExitCode = 0; + status.dwServiceSpecificExitCode = 0; + status.dwCheckPoint = 0; + status.dwWaitHint = 0; + status.dwCurrentState = state; + + SetServiceStatus(svc_handle, &status); +} + +static void WINAPI svc_handler(DWORD control) +{ + TRACE("%#lx\n", control); + + switch (control) + { + case SERVICE_CONTROL_STOP: + case SERVICE_CONTROL_SHUTDOWN: + svc_update_status(SERVICE_STOP_PENDING); + SetEvent(done_event); + break; + + default: + svc_update_status(SERVICE_RUNNING); + break; + } +} + +void WINAPI ServiceMain(DWORD argc, LPWSTR *argv) +{ + TRACE("Starting LanmanServer\n"); + + svc_handle = RegisterServiceCtrlHandlerW(L"LanmanServer", svc_handler); + if (!svc_handle) + { + ERR("RegisterServiceCtrlHandler error %ld\n", GetLastError()); + return; + } + + svc_update_status(SERVICE_START_PENDING); + done_event = CreateEventW(NULL, TRUE, FALSE, NULL); + + svc_update_status(SERVICE_RUNNING); + WaitForSingleObject(done_event, INFINITE); + CloseHandle(done_event); + + svc_update_status(SERVICE_STOPPED); + + TRACE("Exiting LanmanServer\n"); +} diff --git a/dlls/srvsvc/srvsvc.spec b/dlls/srvsvc/srvsvc.spec new file mode 100644 index 00000000000..daa88578f7f --- /dev/null +++ b/dlls/srvsvc/srvsvc.spec @@ -0,0 +1 @@ +@ stdcall -private ServiceMain(long ptr) diff --git a/loader/wine.inf.in b/loader/wine.inf.in index e7b435ed0f0..d686e0b4f2f 100644 --- a/loader/wine.inf.in +++ b/loader/wine.inf.in @@ -2396,12 +2396,12 @@ Description="Lanman Server" DisplayName="Lanman Server" ServiceBinary="%11%\svchost.exe -k netsvcs" ServiceType=32 -StartType=4 +StartType=3 ErrorControl=1 [LanmanServerServiceKeys] HKR,Parameters,"ServiceDll",,"%11%\srvsvc.dll" -;; HKLM,%CurrentVersionNT%\SvcHost,"netsvcs",0x00010008,"lanmanserver" +HKLM,%CurrentVersionNT%\SvcHost,"netsvcs",0x00010008,"lanmanserver" [FontCacheService] AddReg=FontCacheServiceKeys -- 2.37.1

1 0

[PATCH] wevtsvc: Remove duplicate dwControlsAccepted initialization.
by Dmitry Timoshkov 08 Aug '22

08 Aug '22

dwControlsAccepted is initialized a few lines earlier. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/wevtsvc/wevtsvc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/dlls/wevtsvc/wevtsvc.c b/dlls/wevtsvc/wevtsvc.c index 2e303045740..78c68bac69b 100644 --- a/dlls/wevtsvc/wevtsvc.c +++ b/dlls/wevtsvc/wevtsvc.c @@ -40,7 +40,6 @@ static void eventlog_update_status(DWORD state) status.dwServiceSpecificExitCode = 0; status.dwCheckPoint = 0; status.dwWaitHint = 0; - status.dwControlsAccepted = 0; status.dwCurrentState = state; SetServiceStatus(svc_handle, &status); -- 2.37.1

1 0

[PATCH] schedsvc: Remove duplicate dwControlsAccepted initialization.
by Dmitry Timoshkov 08 Aug '22

08 Aug '22

dwControlsAccepted is initialized a few lines earlier. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/schedsvc/svc_main.c | 1 - 1 file changed, 1 deletion(-) diff --git a/dlls/schedsvc/svc_main.c b/dlls/schedsvc/svc_main.c index 7681a220592..2250854e953 100644 --- a/dlls/schedsvc/svc_main.c +++ b/dlls/schedsvc/svc_main.c @@ -281,7 +281,6 @@ static void schedsvc_update_status(DWORD state) status.dwServiceSpecificExitCode = 0; status.dwCheckPoint = 0; status.dwWaitHint = 0; - status.dwControlsAccepted = 0; status.dwCurrentState = state; SetServiceStatus(schedsvc_handle, &status); -- 2.37.1

1 0

Re: [PATCH v8 2/5] winegstreamer: Implement IWMOutputMediaProps_SetMediaType.
by Marvin 08 Aug '22

08 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120665 Your paranoid android. === debian11 (32 bit report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Arabic:Morocco report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit German report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit French report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Hebrew:Israel report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Hindi:India report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Japanese:Japan report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Chinese:China report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit WoW report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (64 bit WoW report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2.

1 0

Wine-Contribution
by Alan 07 Aug '22

07 Aug '22

Hello There i need some help regarding to start applying patches to wine and start contributing the problem is I don't know where to start? I went to the wine website and started reading. I didn't get much useful stuff but There was some good documentation about the codebase and the structure of it , but if I want to start applying patches to wine, where should I start besides the website ? Should I start reading the codebase ? If so, where should I start reading the codebase from ? or should I just go and try to patch the bugs that's on the forks issue section? Thanks For your Time Alan

2 1

Re: [PATCH v4 09/10] mciqtz32: Hide the default video window when switching to another one.
by Marvin 06 Aug '22

06 Aug '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120640 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === winmm: mci.c:1291: Test failed: sysinfo quantity open expected 0 after auto-close, got: 1

1 0

Wine web-based translation using Weblate
by Óvári 06 Aug '22

06 Aug '22

Hello, Can Wine please be available for translation using a browser (eg Firefox) at Weblate? https://hosted.weblate.org/ Thank you On Tue, 19 Jul 2022: [...] > I would have to reassess to be exact but the requirement that caused > issues with most of the systems I investigated was that wine requires > all patches, even translations, to be clearly accredited to a user by > full real name and email. I remember that being the main issue too. But their attribution FAQ says every change is committed under the translators name: https://docs.weblate.org/fr/latest/faq.html#how-does-weblate-credit-transla… | Every change made in Weblate is committed into VCS under the | translators name. This way every single change has proper authorship, | and you can track it down using the standard VCS tools you use for | code. It sounds like this would fulfil Wine's requirement. Also this should probably be posted on wine-devel since it concerns the whole community and would broaden the pool of people who can move forward on this.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel