August 2022 - Wine-Devel - list.winehq.org

Re: [vkd3d] Handling object components within the HLSL compiler.

by Francisco Casas

On 31-08-22 14:12, Zebediah Figura wrote: > I don't think I understand the point of splitting uniforms for sm4 but > not sm1. If we need to determine (and potentially store) the actual type > of a uniform per-component anyway, why would we need to do that > differently for structs and arrays? > Well, first, I don't think we should split uniforms completely, only separate the object components as standalone variables. So, if we have, say struct { float4 foo; Texture2D tex[2]; float4 bar; } pou; We would be effectively end up with 3 variables: The original: --- struct { float4 foo; Texture2D tex[2]; float4 bar; } pou; --- and: --- Texture2D "pou.tex[0]"; Texture2D "pou.tex[1]"; --- because we would be adding a store from the "pou.tex[0]" variable to pou.tex[0], and from the "pou.tex[1]" variable to pou.tex[1], copy-prop should replace all derefs to the Texture components to derefs to these new variables. The pou variable no longer has to worry about the register allocation of its Texture fields, because the new variables do that. Generalizing, variables should no longer care about their object components, unless they are objects themselves. I think something similar happens under the hood in SM4, consider the output of the following shader in the native compiler: --- struct { float4 foo; Texture2D tex[2]; float4 bar; } pou; float4 main() : SV_TARGET { return pou.bar + pou.tex[0].Load(int3(1, 2, 3)) + pou.tex[1].Load(int3(1, 2, 3)); } --- --- // Buffer Definitions: // // cbuffer $Globals // { // // struct <unnamed> // { // // float4 foo; // Offset: 0 // float4 bar; // Offset: 16 // // } pou; // Offset: 0 Size: 32 // Textures: t0-t1 // // } // // // Resource Bindings: // // Name Type Format Dim HLSL Bind Count // --------------------- ---------- ------- -------- --------- ------ // pou.tex[0] texture float4 2d t0 1 // pou.tex[1] texture float4 2d t1 1 // $Globals cbuffer NA NA cb0 1 --- Object components are listed separately in the resource bindings, and they are efectively removed (or ignored?) in the definition of pou. Now, regarding SM1, it is not possible to declare objects inside other components, it is only possible to create (possibly multi-dimensional) arrays of single object types: --- sampler sam[3][2]; float4 main() : SV_TARGET { return tex2D(sam[2][1], float2(1, 2)); } --- but they don't appear as different variables in the CTAB section: --- // Parameters: // // sampler2D sam[6]; // // // Registers: // // Name Reg Size // ------------ ----- ---- // sam s0 6 // --- Unlike in SM4: --- // Resource Bindings: // // Name Type Format Dim Slot Elements // ------------------------ -------- ------- ------ ---- -------- // sam[2][1] sampler NA NA 5 1 // sam[2][1] texture float4 2d 5 1 --- (to get this output I used fxc 9 with compatibility mode) So, in summary, my idea is to: - For SM4, separate object components as stand-alone variables that take care of the register allocation of these individual objects. - For SM1, just support (possibly multi-dimensional) object arrays. With this, for both SM1 and SM4, each variable should only care about the allocation of a single type of register, so we can use the register offsets as we do now. In the future we would probably want to remove the "offset" field from the derefs, and make each hlsl_sm*.c compute the register offsets from the derefs in their index path form.

Aug. 31, 2022

Re: RFC: Allow marking unreliable tests as flaky.

by Alexandre Julliard

Francois Gouget <fgouget(a)codeweavers.com> writes: > On Wed, 1 Jun 2022, Rémi Bernon wrote: > [...] >> I think flaky_if should be enough, and then there could be some shortcut >> global variables for `!strcmp(winetest_platform, "windows" / "wine")`, so it's >> not too long to write. > > So: flaky_if( is_windows ) > flaky_if( is_wine ) > and plain flaky() I think flaky_wine is better. I don't see a need for flaky_windows though, there's no reason to enforce that a test should always succeed on Wine if it doesn't on Windows. -- Alexandre Julliard julliard(a)winehq.org

Aug. 31, 2022

Re: [vkd3d] Handling object components within the HLSL compiler.

by Zebediah Figura

On 8/30/22 18:05, Francisco Casas wrote: > > 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. I don't think I understand the point of splitting uniforms for sm4 but not sm1. If we need to determine (and potentially store) the actual type of a uniform per-component anyway, why would we need to do that differently for structs and arrays?

Aug. 31, 2022

Re: Puzzling IPrincipal:UserId check in taskschd

by Dmitry Timoshkov

Francois Gouget <fgouget(a)free.fr> wrote: > 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); I'd guess the check is supposed to avoid writing an empty UserId, and apparently the check for bstr being NULL is not enough. I don't recall why writing empty UserId is different from other property values. -- Dmitry.

Aug. 31, 2022

Re: RFC: Allow marking unreliable tests as flaky.

by Rémi Bernon

On 8/31/22 18:20, Francois Gouget wrote: > On Wed, 1 Jun 2022, Rémi Bernon wrote: > [...] >> Imho the message should keep the 'Test failed' / 'Test succeeded' prefixes. >> For instance I think it would look more consistent with something like: >> >> Test succeeded inside todo block: > > This is a non flaky todo test which succeeds. > >> Test succeeded inside flaky block: > > The message does not reflect that such a test is both flaky *and* > todo. Mabe something like this would be clearer: > > Test succeeded inside flaky todo block: > > >> Test marked todo: >> Test marked flaky: >> Test failed: >> Test succeeded: > > That can work. > > > [...] >> I think flaky_if should be enough, and then there could be some shortcut >> global variables for `!strcmp(winetest_platform, "windows" / "wine")`, so it's >> not too long to write. > > So: flaky_if( is_windows ) > flaky_if( is_wine ) > and plain flaky() > > I worry that we would risk name collisions but winetest_is_windows would > defeat the purpose. (plus we already have some short potentially > collision-prone names and it worked out so far) > > It's tempting to have things line is_win10 but again that's likely > either too fine grained or not enough which probably makes it useless > (is_win10_2009_or_greater). > Yeah I don't think we need something finer for the most common cases. And I believe we're trying to avoid having tests checking Windows versions in general, using feature checks instead. -- Rémi Bernon <rbernon(a)codeweavers.com>

Aug. 31, 2022

Re: RFC: Allow marking unreliable tests as flaky.

by Francois Gouget

On Wed, 1 Jun 2022, Rémi Bernon wrote: [...] > Imho the message should keep the 'Test failed' / 'Test succeeded' prefixes. > For instance I think it would look more consistent with something like: > > Test succeeded inside todo block: This is a non flaky todo test which succeeds. > Test succeeded inside flaky block: The message does not reflect that such a test is both flaky *and* todo. Mabe something like this would be clearer: Test succeeded inside flaky todo block: > Test marked todo: > Test marked flaky: > Test failed: > Test succeeded: That can work. [...] > I think flaky_if should be enough, and then there could be some shortcut > global variables for `!strcmp(winetest_platform, "windows" / "wine")`, so it's > not too long to write. So: flaky_if( is_windows ) flaky_if( is_wine ) and plain flaky() I worry that we would risk name collisions but winetest_is_windows would defeat the purpose. (plus we already have some short potentially collision-prone names and it worked out so far) It's tempting to have things line is_win10 but again that's likely either too fine grained or not enough which probably makes it useless (is_win10_2009_or_greater). -- Francois Gouget <fgouget(a)codeweavers.com>

Aug. 31, 2022

Puzzling IPrincipal:UserId check in taskschd

by Francois Gouget

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

Aug. 31, 2022

Whenever i use wine this message pop up and the application doesn't run please any help

by anthonyuser33

Sent from my Galaxy

Aug. 31, 2022

[vkd3d] Handling object components within the HLSL compiler.

by Francisco Casas

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. ```

Aug. 30, 2022

Wine staging 7.16 release

by Alistair Leslie-Hughes

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.

Aug. 29, 2022

Re: [PATCH 1/2] readme: Update Finnish translation.

by Bernhard Kölbl

Hi, just fyi, all patches need to be submitted through Gitlab now. Thanks Bernhard Lauri Kenttä <lauri.kentta(a)gmail.com> schrieb am Do., 25. Aug. 2022, 09:03: > 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 > > >

Aug. 29, 2022

[PATCH 2/2] po: Update Finnish translation.

by Lauri Kenttä

Signed-off-by: Lauri Kenttä <lauri.kentta(a)gmail.com> --- po/fi.po | 68 +++++--------------------------------------------------- 1 file changed, 5 insertions(+), 63 deletions(-) diff --git a/po/fi.po b/po/fi.po index ca7ca5c5b9d..e913097eb00 100644 --- a/po/fi.po +++ b/po/fi.po @@ -1327,10 +1327,8 @@ msgid "Options" msgstr "Valinnat" #: dlls/compstui/compstui.rc:31 -#, fuzzy -#| msgid "Defaults" msgid "Default" -msgstr "Oletukset" +msgstr "Oletus" #: dlls/credui/credui.rc:45 msgid "&User name:" @@ -15825,56 +15823,6 @@ msgstr "" "\n" #: programs/reg/reg.rc:67 -#, fuzzy -#| msgid "" -#| "REG ADD <key> [/v value_name | /ve] [/t type] [/s separator] [/d data] [/" -#| "f]\n" -#| "\n" -#| " Adds a key to the registry or adds a new value to a given registry " -#| "key.\n" -#| "\n" -#| " <key>\n" -#| " The registry key to add or, if either [/v] or [/ve] is specified,\n" -#| " the key in which to add the new registry data.\n" -#| "\n" -#| " Format: ROOT\\Subkey\n" -#| "\n" -#| " ROOT: A predefined registry key. This must be one of the following:\n" -#| "\n" -#| " HKEY_LOCAL_MACHINE | HKLM\n" -#| " HKEY_CURRENT_USER | HKCU\n" -#| " HKEY_CLASSES_ROOT | HKCR\n" -#| " HKEY_USERS | HKU\n" -#| " HKEY_CURRENT_CONFIG | HKCC\n" -#| "\n" -#| " Subkey: The full path to a registry key under a given ROOT key.\n" -#| "\n" -#| " /v <value_name>\n" -#| " The name of the registry value to add.\n" -#| "\n" -#| " /ve\n" -#| " Add an unnamed registry value. This option modifies the (Default)\n" -#| " registry value.\n" -#| "\n" -#| " /t <type>\n" -#| " The type of data to add to the registry. If [/t] is specified,\n" -#| " <type> must be one of the following:\n" -#| "\n" -#| " REG_SZ | REG_MULTI_SZ | REG_EXPAND_SZ\n" -#| " REG_DWORD | REG_BINARY | REG_NONE\n" -#| "\n" -#| " If [/t] is not specified, the default data type is REG_SZ.\n" -#| "\n" -#| " /s <separator>\n" -#| " The character used to separate strings in REG_MULTI_SZ data.\n" -#| " If [/s] is not specified, the default separator is \\0.\n" -#| "\n" -#| " /d <data>\n" -#| " The data to add to the new registry value.\n" -#| "\n" -#| " /f\n" -#| " Modify the registry without prompting for confirmation.\n" -#| "\n" msgid "" "REG ADD <key> [/v value_name | /ve] [/t type] [/s separator] [/d data] [/f]\n" "\n" @@ -15954,7 +15902,7 @@ msgstr "" " seuraavista:\n" "\n" " REG_SZ | REG_MULTI_SZ | REG_EXPAND_SZ\n" -" REG_DWORD | REG_BINARY | REG_NONE\n" +" REG_DWORD | REG_QWORD | REG_BINARY | REG_NONE\n" "\n" " Jos parametria [/t] ei anneta, datan laji on oletuksena REG_SZ.\n" "\n" @@ -16391,10 +16339,8 @@ msgstr "&DWORD-arvo" #: programs/regedit/regedit.rc:52 programs/regedit/regedit.rc:105 #: programs/regedit/regedit.rc:128 -#, fuzzy -#| msgid "&DWORD Value" msgid "&QWORD Value" -msgstr "&DWORD-arvo" +msgstr "&QWORD-arvo" #: programs/regedit/regedit.rc:53 programs/regedit/regedit.rc:106 #: programs/regedit/regedit.rc:129 @@ -16947,16 +16893,12 @@ msgid "Collapse" msgstr "Tiivistä" #: programs/regedit/regedit.rc:178 -#, fuzzy -#| msgid "Adds a new 32-bit value" msgid "Adds a new 64-bit value" -msgstr "Lisää uuden 32-bittisen arvon" +msgstr "Lisää uuden 64-bittisen arvon" #: programs/regedit/regedit.rc:221 -#, fuzzy -#| msgid "Edit DWORD" msgid "Edit QWORD" -msgstr "Muokkaa DWORD-arvoa" +msgstr "Muokkaa QWORD-arvoa" #: programs/regsvr32/regsvr32.rc:33 msgid "" -- 2.37.2

Aug. 25, 2022

[PATCH 1/2] readme: Update Finnish translation.

by Lauri Kenttä

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

Aug. 25, 2022

Upcoming vkd3d 1.5 release.

by Henri Verbeet

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

Aug. 24, 2022

wine-devel moved to Mailman3

by Jeremy Newman

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(a)winehq.org/ The old archives will remain online to preserve links. -N

Aug. 22, 2022

WINE and Haxial programs

by haxial

Hi There My company produces a few programs that run on Windows and MacOS. Some of the users of these programs have been experimenting using WINE to run the programs on Linux. This is what they have been saying: "the KDX server runs FLAWLESSLY, 100% perfect, better than solitaire runs" However, there is one caveat to the above: I'm told that text input doesn't work when running KDX using WINE on Linux. I was wondering if I would be able to work with WINE developers in making KDX run perfectly on Linux using WINE. I think you would find this to be an easier task than usual because KDX only uses a *minimal* amount of windoze APIs. For example, KDX implements it's own GUI, it does not use the windoze API for that. Also, KDX even implements it's own graphics routines, it does not use the windoze GDI functions (except for the final step of getting the images onto the screen). KDX loads no obscure DLL's, it's just a single .exe file. It does not use MDI or any crap like that. It does not access the registry. It does not use MFC. So I think it would be much easier for WINE than your average windoze program. Which probably explains why it's already running well, except there is some bug, probably a minor little thing, that is preventing text input from working. The website is: http://www.haxial.com Thanks.

Aug. 22, 2022

Re: [PATCH 1/2] user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.

by Dmitry Timoshkov

Hi Esme, "Esme Povirk (she/they)" <esme(a)codeweavers.com> wrote: > With the patch tracker retired, patches have to go through gitlab now. Do I understand correctly that now in order to send even simple patch one needs to go through full MR creation process, starting with the registration step? Isn't that backwards to an idea of making Wine developer audience wider, and making sending patches to Wine comfortable for everyone? If the idea is to make sending even trivial fixes harder, then I don't quite follow the intents... -- Dmitry.

Aug. 18, 2022

Re: [PATCH 1/2] user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.

by Esme Povirk (she/they)

With the patch tracker retired, patches have to go through gitlab now. On Thu, Aug 18, 2022 at 8:33 AM Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > > 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 > >

Aug. 18, 2022

[PATCH 2/2] user32: Set font charset to DEFAULT_CHARSET to support locale change.

by Dmitry Timoshkov

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

Aug. 18, 2022

[PATCH 1/2] user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.

by Dmitry Timoshkov

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

Aug. 18, 2022

wine-cvs renamed to wine-commits

by Jeremy Newman

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

Aug. 17, 2022

Re: Patch tracker

by Zebediah Figura (she/her)

On 8/16/22 15:04, Alexandre Julliard wrote: > "Zebediah Figura (she/her)" <zfigura(a)codeweavers.com> writes: > >> On 8/15/22 05:23, Alexandre Julliard wrote: >>> 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. >> >> I didn't realize this meant retiring the patch tracker page. Is that >> necessary? Is there a chance it can be restored? It's faster and >> better UI than either gitlab web UI or command-line tools. > > Yes, it's necessary, I'm not going to continue to maintain a parallel > file-based database for the status of every patch, especially since it > was really a hack put together with Elisp and duct tape. > Okay. I figured it would be fine to keep around since there wasn't any need to manually update patch status, but I understand the need to remove old code.

Aug. 16, 2022

Re: Patch tracker

by Alexandre Julliard

"Zebediah Figura (she/her)" <zfigura(a)codeweavers.com> writes: > On 8/15/22 05:23, Alexandre Julliard wrote: >> 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. > > I didn't realize this meant retiring the patch tracker page. Is that > necessary? Is there a chance it can be restored? It's faster and > better UI than either gitlab web UI or command-line tools. Yes, it's necessary, I'm not going to continue to maintain a parallel file-based database for the status of every patch, especially since it was really a hack put together with Elisp and duct tape. -- Alexandre Julliard julliard(a)winehq.org

Aug. 16, 2022

Re: Patch tracker

by Zebediah Figura (she/her)

On 8/15/22 05:23, Alexandre Julliard wrote: > 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. I didn't realize this meant retiring the patch tracker page. Is that necessary? Is there a chance it can be restored? It's faster and better UI than either gitlab web UI or command-line tools.

Aug. 16, 2022

Re: Patch tracker

by Alexandre Julliard

Gijs Vermeulen <gijsvrm(a)gmail.com> writes: > On Mon, Aug 15, 2022, 12:23 Alexandre Julliard <julliard(a)winehq.org> wrote: > > 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. > > As the patch tracker has now been disabled, what is the future of the wine-gitlab list? The list will stay around, as long as people find it useful. -- Alexandre Julliard julliard(a)winehq.org

Aug. 16, 2022

Re: Patch tracker

by Gijs Vermeulen

On Mon, Aug 15, 2022, 12:23 Alexandre Julliard <julliard(a)winehq.org> wrote: > 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. > As the patch tracker has now been disabled, what is the future of the wine-gitlab list? >

Aug. 16, 2022

Re: Patch tracker

by Alexandre Julliard

Bernhard Kölbl <besentv(a)gmail.com> writes: > Hey, > > Am Mo., 15. Aug. 2022 um 12:23 Uhr schrieb Alexandre Julliard > <julliard(a)winehq.org>: >> >> - Adding a Signed-off-by header is no longer necessary. This is >> replaced by the Gitlab approval mechanism. > >> >> - In general, approving your own MR is not necessary or useful. >> > > So the replacement of Sign-Offs with self approving your MR is dropped > now, if I understand correctly? Yes. Self-approving your MR is only for the case where a commit is written by someone else. -- Alexandre Julliard julliard(a)winehq.org

Aug. 15, 2022

Re: Patch tracker

by Bernhard Kölbl

Hey, Am Mo., 15. Aug. 2022 um 12:23 Uhr schrieb Alexandre Julliard <julliard(a)winehq.org>: > > - Adding a Signed-off-by header is no longer necessary. This is > replaced by the Gitlab approval mechanism. > > - In general, approving your own MR is not necessary or useful. > So the replacement of Sign-Offs with self approving your MR is dropped now, if I understand correctly? (This was done for some time iirc) Thanks, Bernhard

Aug. 15, 2022

Patch tracker

by Alexandre Julliard

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

Aug. 15, 2022

Re: Re: [PATCH v2 1/2] qedit: Add test for adding a reference during callback

by Marvin

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=121193 Your paranoid android. === build (build log) === error: patch failed: dlls/qedit/tests/mediadet.c:866 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/qedit/tests/mediadet.c:866 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/qedit/tests/mediadet.c:866 Task: Patch failed to apply

Aug. 15, 2022

Re: [PATCH v2 1/2] qedit: Add test for adding a reference during callback

by Brendan McGrath

On 15/7/22 05:02, David Kahurani wrote: > On Sat, Jul 9, 2022 at 9:52 AM Brendan McGrath<brendan(a)redmandi.com> wrote: >> Unravel Two adds a reference to the IMediaSample during its callback. >> >> This patch adds a test that checks if an application does do this, that it can >> free it later and the reference count will finish at zero. >> >> Wine-Bug:https://bugs.winehq.org/show_bug.cgi?id=51616 >> Signed-off-by: Brendan McGrath<brendan(a)redmandi.com> >> --- >> >> Thanks Zeb for taking a look. Agree with your feedback. I guess we need >> to prove the workaround is incorrect. >> >> This test I think replicates what Unravel Two does, and it does demonstrate >> that the workaround will cause an issue in this scenario. >> >> But it would be good to hear back from the original author; although 12 >> years is a long time! >> >> Unrelated to this patchset - but I noticed I get a seg fault when running the >> mediadet tests (the others seem ok). It happens right at the end: >> Segmentation fault (core dumped) >> make: *** [Makefile:120413: dlls/qedit/tests/mediadet.ok] Error 139 >> >> I didn't see it on the Wine test servers, but I'm wondering if you get >> the same when you run locally? > Yes, I also get that. I've created a wine bug for this: https://bugs.winehq.org/show_bug.cgi?id=53556 I've added a lot more detail there, and an experimental fix. I'd be curious to know if the segfault you are seeing is the same thing. >> Anyway, thanks again. Appreciate your time. >> >> >> dlls/qedit/tests/mediadet.c | 27 ++++++++++++++++++++++----- >> 1 file changed, 22 insertions(+), 5 deletions(-) >> >> diff --git a/dlls/qedit/tests/mediadet.c b/dlls/qedit/tests/mediadet.c >> index 3202baca9244..3ea752176618 100644 >> --- a/dlls/qedit/tests/mediadet.c >> +++ b/dlls/qedit/tests/mediadet.c >> @@ -866,6 +866,11 @@ static void test_put_filter(void) >> ok(!ref, "Got outstanding refcount %ld.\n", ref); >> } >> >> +struct MySample { >> + IMediaSample sample; >> + LONG refcount; >> +}; >> + >> static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, >> void **ppvObject) >> { >> @@ -874,12 +879,18 @@ static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, >> >> static ULONG WINAPI ms_AddRef(IMediaSample *iface) >> { >> - return 2; >> + struct MySample *my_sample = (struct MySample*) iface; >> + ULONG refcount = InterlockedIncrement(&my_sample->refcount); >> + >> + return refcount; >> } >> >> static ULONG WINAPI ms_Release(IMediaSample *iface) >> { >> - return 1; >> + struct MySample *my_sample = (struct MySample*) iface; >> + ULONG refcount = InterlockedDecrement(&my_sample->refcount); >> + >> + return refcount; >> } >> >> static HRESULT WINAPI ms_GetPointer(IMediaSample *iface, BYTE **ppBuffer) >> @@ -989,7 +1000,7 @@ static const IMediaSampleVtbl my_sample_vt = { >> ms_SetMediaTime >> }; >> >> -static IMediaSample my_sample = { &my_sample_vt }; >> +static struct MySample my_sample = { {&my_sample_vt}, 0 }; >> >> static BOOL samplecb_called = FALSE; >> >> @@ -1012,8 +1023,9 @@ static ULONG WINAPI sgcb_Release(ISampleGrabberCB *iface) >> static HRESULT WINAPI sgcb_SampleCB(ISampleGrabberCB *iface, double SampleTime, >> IMediaSample *pSample) >> { >> - ok(pSample == &my_sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); >> + ok(pSample == &my_sample.sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); >> samplecb_called = TRUE; >> + IMediaSample_AddRef(pSample); >> return E_NOTIMPL; >> } >> >> @@ -1043,6 +1055,7 @@ static void test_samplegrabber(void) >> IEnumPins *pins; >> HRESULT hr; >> FILTER_STATE fstate; >> + ULONG refcount; >> >> /* Invalid RIID */ >> hr = CoCreateInstance(&CLSID_SampleGrabber, NULL, CLSCTX_INPROC_SERVER, &IID_IClassFactory, >> @@ -1074,10 +1087,14 @@ static void test_samplegrabber(void) >> hr = IPin_QueryInterface(pin, &IID_IMemInputPin, (void**)&inpin); >> ok(hr == S_OK, "Got hr %#lx.\n", hr); >> >> - hr = IMemInputPin_Receive(inpin, &my_sample); >> + hr = IMemInputPin_Receive(inpin, &my_sample.sample); >> ok(hr == S_OK, "Got hr %#lx.\n", hr); >> ok(samplecb_called == TRUE, "SampleCB should have been called\n"); >> >> + // Release the Ref we added in the callback >> + refcount = IUnknown_Release(&my_sample.sample); >> + todo_wine ok(refcount == 0, "refcount should be zero\n"); >> + >> IMemInputPin_Release(inpin); >> IPin_Release(pin); >> >> -- >> 2.34.1 >> >>

Aug. 15, 2022

Wine staging 7.15 release

by Alistair Leslie-Hughes

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.

Aug. 14, 2022

Re: [PATCH v2 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.

by Marvin

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.

Aug. 12, 2022

Re: [PATCH v2 2/3] d3d11: Always return E_FAIL for formats which have no support flags.

by Marvin

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.

Aug. 12, 2022

Re: [PATCH v2 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.

by Marvin

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.

Aug. 12, 2022

Re: [PATCH 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.

by Marvin

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).

Aug. 11, 2022

Re: [PATCH 2/3] d3d11: Always return E_FAIL for formats which have no support flags.

by Marvin

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).

Aug. 11, 2022

Re: [PATCH 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.

by Marvin

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).

Aug. 11, 2022

Re: [PATCH 1/6] mshtml: Forward Document's Invoke to InvokeEx.

by Marvin

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

Aug. 11, 2022

Re: WineConf 2022 - Bring out your talks

by Francois Gouget

On Mon, 8 Aug 2022, Jeremy White wrote: [...] > 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/ Given that the conference will have non-Wine attendants it could be nice to have a "Why Wine is important : 20 years later" talk. Where 20 years later is because that last talk was at the very first WineConf, in 2002. However the situation has changed somewhat since then, what ith Web 2.0, smartphones, tablets and Chromebooks. So I'm not voluntering for this one. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ You don't liberate a people. A people liberates itself. Youssoupha

Aug. 11, 2022

Re: [PATCH v2 4/6] mf: Allow resolving topology with missing downstream current type.

by Marvin

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

Aug. 11, 2022

Re: [PATCH 1/5] comctl32/tests: Add IME tests for edit control.

by Marvin

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

Aug. 11, 2022

Re: [PATCH v3 1/2] mshtml: Semi-implement non-string primitive data for postMessage.

by Marvin

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

Aug. 10, 2022

Re: [PATCH v5 01/10] winmm/tests: Add tests for visibility of video window.

by Marvin

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

Aug. 10, 2022

Re: [PATCH v4 03/13] mmdevapi: Integrate winepulse's additions in unixlib.h

by Marvin

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

Aug. 10, 2022

Re: [PATCH 1/1] d3d11: Validate layout description in d3d_input_layout_create().

by Marvin

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.

Aug. 9, 2022

Re: [PATCH v2 1/2] mshtml: Semi-implement non-string primitive data for postMessage.

by Marvin

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

Aug. 9, 2022

WinRt activable class registration

by Kacper rączy

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

Aug. 9, 2022

Re: [PATCH 2/2] ntdll: Fix leak of mach_host_self port.

by Marvin

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

Aug. 8, 2022

Re: [PATCH v2 1/2] mf: Handle timer time behind clock time in present_clock_schedule_timer().

by Marvin

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

Aug. 8, 2022

WineConf 2022 - Bring out your talks

by Jeremy White

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/.

Aug. 8, 2022

[PATCH] srvsvc: Add LanmanServer stub service.

by Dmitry Timoshkov

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

Aug. 8, 2022

[PATCH] wevtsvc: Remove duplicate dwControlsAccepted initialization.

by Dmitry Timoshkov

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

Aug. 8, 2022

[PATCH] schedsvc: Remove duplicate dwControlsAccepted initialization.

by Dmitry Timoshkov

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

Aug. 8, 2022

Re: [PATCH v8 2/5] winegstreamer: Implement IWMOutputMediaProps_SetMediaType.

by Marvin

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.

Aug. 8, 2022

Re: Wine-Contribution

by Bernhard Kölbl

Hi, https://wiki.winehq.org/Wine_Developer%27s_Guide should be helpful. Other than that, you should familiarize yourself with the code by for example debugging a broken program. Thanks, Bernhard Alan <alan1010035(a)gmail.com> schrieb am Sa., 6. Aug. 2022, 11:55: > 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 >

Aug. 7, 2022

Re: [PATCH v4 09/10] mciqtz32: Hide the default video window when switching to another one.

by Marvin

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

Aug. 6, 2022

Wine web-based translation using Weblate

by Óvári

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.

Aug. 6, 2022

Wine-Contribution

by Alan

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

Aug. 5, 2022

Re: [PATCH v7 1/5] wmvcore/tests: Add some IWMOutputMediaProps_SetMediaType tests.

by Marvin

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=120582 Your paranoid android. === debian11 (32 bit report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Arabic:Morocco report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit German report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit French report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Hebrew:Israel report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Hindi:India report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Japanese:Japan report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Chinese:China report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit WoW report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (64 bit WoW report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0.

Aug. 5, 2022

Re: [PATCH vkd3d v3 13/17] vkd3d-shader/hlsl: Replace register offsets with index paths in resource loads initialization.

by Francisco Casas

Ah, I finally see, the hlsl_src_from_node(&deref->offset, other->offset.node); indeed is a noop. I will fix it. On 25-07-22 04:11, Giovanni Mascellani wrote: > Hi, > > Il 22/07/22 20:36, Francisco Casas ha scritto: >>>> diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c >>>> index 2d5fe40a..a4d594b7 100644 >>>> --- a/libs/vkd3d-shader/hlsl.c >>>> +++ b/libs/vkd3d-shader/hlsl.c >>>> @@ -862,6 +862,28 @@ static bool type_is_single_reg(const struct >>>> hlsl_type *type) >>>> return type->type == HLSL_CLASS_SCALAR || type->type == >>>> HLSL_CLASS_VECTOR; >>>> } >>>> +static bool deref_copy(struct hlsl_ctx *ctx, struct hlsl_deref >>>> *deref, struct hlsl_deref *other) >>>> +{ >>>> + unsigned int i; >>>> + >>>> + memset(deref, 0, sizeof(*deref)); >>>> + >>>> + if (!other) >>>> + return true; >>>> + >>>> + assert(!other->offset.node); >>>> + >>>> + if (!init_deref(ctx, deref, other->var, other->path_len)) >>>> + return false; >>>> + >>>> + for (i = 0; i < deref->path_len; ++i) >>>> + hlsl_src_from_node(&deref->path[i], other->path[i].node); >>>> + >>>> + hlsl_src_from_node(&deref->offset, other->offset.node); >>> >>> You just asserted that other->offset.node is NULL and *deref was >>> initialized to zero, so that seems to be a noop, doesn't it? >>> >> >> Hmm, sorry, I am not sure I understand. >> Initializing *deref to zero shouldn't affect >> >> assert(!other->offset.node); >> >> The idea of this assertion is to ensure that the "other" deref is in >> the index path format instead of the register offset format. > > My point is that, given that you just asserted that other->offset.node > is NULL, the effect of "hlsl_src_from_node(&deref->offset, > other->offset.node)" would be to set deref->offset.node to NULL, but > that's already ensured by the memset(). Or maybe I am getting confused > on something trivial? > > Giovanni.

Aug. 4, 2022

Re: [PATCH vkd3d v3 16/17] vkd3d-shader/hlsl: Replace register offsets with index paths in input/output copies.

by Matteo Bruni

On Thu, Aug 4, 2022 at 9:10 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: > > Hello, > > On 28-07-22 16:59, Matteo Bruni wrote: > > On Wed, Jul 20, 2022 at 3:24 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: > >> > >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> > >> --- > >> > >> v3: > >> * No changes. > >> > >> The recursive structure of prepend_input_var_copy() and > >> append_output_var_copy() could be preserved creating additional > >> loads to complete the paths. Otherwise we would be requiring > >> passing whole paths as arguments. > >> > >> These additional loads should be handled by DCE. > >> > >> Still, matrix vectors are copied iteratively instead of recursively now, > >> to avoid the boilerplate of creating new loads in this last step. > >> > >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> > >> --- > >> libs/vkd3d-shader/hlsl_codegen.c | 188 +++++++++++++++++++------------ > >> 1 file changed, 116 insertions(+), 72 deletions(-) > >> > >> diff --git a/libs/vkd3d-shader/hlsl_codegen.c b/libs/vkd3d-shader/hlsl_codegen.c > >> index 6437006b..7a245007 100644 > >> --- a/libs/vkd3d-shader/hlsl_codegen.c > >> +++ b/libs/vkd3d-shader/hlsl_codegen.c > >> @@ -239,59 +239,75 @@ static struct hlsl_ir_var *add_semantic_var(struct hlsl_ctx *ctx, struct hlsl_ir > >> return ext_var; > >> } > >> > >> -static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, > >> - struct hlsl_type *type, unsigned int field_offset, unsigned int modifiers, const struct hlsl_semantic *semantic) > >> +static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_load *lhs, > >> + struct hlsl_type *type, unsigned int modifiers, const struct hlsl_semantic *semantic) > > > > I haven't put a lot of thought into this, but it seems to me we could > > pass a deref instead of a redundant load and be mostly set. Mostly > > because we then need to add the instructions to the instruction list > > in some other way (e.g. by passing an explicit list). > > I tried it passing a hlsl_blocks to be initialized (like in the > component load/store initializers) but in the end it didn't seem like a > good idea to me: > > The problem is that we would need to create derefs in the wild (outside > hlsl_ir_nodes), which would mean exposing several static functions in > hlsl.c, like init_deref_from_component_index(). We would also need to > use "hlsl_cleanup_deref()" which for now is only non-static because it > is needed in the the pass that translates index paths back to register > offsets. > > So I don't think exposing the deref functions is better than adding > these redundant loads, which are later deleted by the DCE pass, if I am > not mistaken. > > Alternatively, we could create the nodes just as a container for the > derefs and immediately free them, but that also seems a little ugly. > > So my vote is to keep this signature. Maybe remove the "type" parameter > since it can be obtained from the deref inside the load node. Fair enough. That was hard to see without actually trying and it sounds like redundant loads are the lesser evil in this case. Maybe a comment somewhere explaining that these loads are redundant and supposed to be eliminated by DCE would be nice.

Aug. 4, 2022

Re: [PATCH vkd3d v3 16/17] vkd3d-shader/hlsl: Replace register offsets with index paths in input/output copies.

by Francisco Casas

Hello, On 28-07-22 16:59, Matteo Bruni wrote: > On Wed, Jul 20, 2022 at 3:24 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: >> >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> >> --- >> >> v3: >> * No changes. >> >> The recursive structure of prepend_input_var_copy() and >> append_output_var_copy() could be preserved creating additional >> loads to complete the paths. Otherwise we would be requiring >> passing whole paths as arguments. >> >> These additional loads should be handled by DCE. >> >> Still, matrix vectors are copied iteratively instead of recursively now, >> to avoid the boilerplate of creating new loads in this last step. >> >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> >> --- >> libs/vkd3d-shader/hlsl_codegen.c | 188 +++++++++++++++++++------------ >> 1 file changed, 116 insertions(+), 72 deletions(-) >> >> diff --git a/libs/vkd3d-shader/hlsl_codegen.c b/libs/vkd3d-shader/hlsl_codegen.c >> index 6437006b..7a245007 100644 >> --- a/libs/vkd3d-shader/hlsl_codegen.c >> +++ b/libs/vkd3d-shader/hlsl_codegen.c >> @@ -239,59 +239,75 @@ static struct hlsl_ir_var *add_semantic_var(struct hlsl_ctx *ctx, struct hlsl_ir >> return ext_var; >> } >> >> -static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, >> - struct hlsl_type *type, unsigned int field_offset, unsigned int modifiers, const struct hlsl_semantic *semantic) >> +static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_load *lhs, >> + struct hlsl_type *type, unsigned int modifiers, const struct hlsl_semantic *semantic) > > I haven't put a lot of thought into this, but it seems to me we could > pass a deref instead of a redundant load and be mostly set. Mostly > because we then need to add the instructions to the instruction list > in some other way (e.g. by passing an explicit list). I tried it passing a hlsl_blocks to be initialized (like in the component load/store initializers) but in the end it didn't seem like a good idea to me: The problem is that we would need to create derefs in the wild (outside hlsl_ir_nodes), which would mean exposing several static functions in hlsl.c, like init_deref_from_component_index(). We would also need to use "hlsl_cleanup_deref()" which for now is only non-static because it is needed in the the pass that translates index paths back to register offsets. So I don't think exposing the deref functions is better than adding these redundant loads, which are later deleted by the DCE pass, if I am not mistaken. Alternatively, we could create the nodes just as a container for the derefs and immediately free them, but that also seems a little ugly. So my vote is to keep this signature. Maybe remove the "type" parameter since it can be obtained from the deref inside the load node.

Aug. 4, 2022

Re: [PATCH vkd3d v3 17/17] vkd3d-shader/hlsl: Replace register offsets with index paths in split copies.

by Francisco Casas

Hello, On 28-07-22 17:00, Matteo Bruni wrote: >> static bool split_copy(struct hlsl_ctx *ctx, struct hlsl_ir_store *store, >> - const struct hlsl_ir_load *load, const unsigned int offset, struct hlsl_type *type) >> + const struct hlsl_ir_load *load, const unsigned int indx, struct hlsl_type *type) > > Why "indx" now? The rename is because I don't want to get it confused with "offset" as in "register offset", since it is a "component index" now. In case you meant why I wrote "indx" instead of "idx", which seems to be the standard, it was just a mistake, I will change it.

Aug. 4, 2022

Re: [PATCH v8 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.

by Marvin

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=120511 Your paranoid android. === w10pro64 (32 bit report) === user32: win.c:10984: Test failed: pos = 014a015e

Aug. 4, 2022

Re: [PATCH v8 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.

by Marvin

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=120510 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === user32: win.c:4592: Test failed: hwnd 00000000001F0326/00000000001F0326 message 0200 win.c:4595: Test failed: hwnd 00000000001F0326/00000000001F0326 message 0201 === w10pro64_ar (64 bit report) === user32: win.c:4641: Test failed: hwnd 00000000000B02D2/00000000000B02D2 message 0200 win.c:4643: Test failed: wparam 0 win.c:4654: Test failed: hwnd 00000000000B02D2/00000000000B02D2 message 0203 win.c:4658: Test failed: message 0202 available

Aug. 4, 2022

Re: [PATCH vkd3d v3 09/17] vkd3d-shader/hlsl: Replace register offsets with index paths in load initializations.

by Giovanni Mascellani

Il 02/08/22 22:25, Matteo Bruni ha scritto: >> BTW, an alternative name for the function could be >> 'traverse_path_from_component_index', but I am not totally sure. > Also good, it feels like an improvement to me. > > I wonder what Zeb and Giovanni think about this (if anything) 😄 No specific thought, so it's good. Giovanni.

Aug. 4, 2022

Re: [PATCH vkd3d 05/17] vkd3d-shader/hlsl: Introduce add_load_component().

by Matteo Bruni

On Wed, Aug 3, 2022 at 11:26 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: > > > > On 28-07-22 16:44, Matteo Bruni wrote: > > Okay, I guess I managed to read the patch series through. Sorry it > > took me way longer than I'd hoped, and I didn't even properly review > > the individual patches (e.g. apply them and check that the tests pass > > after each one). > > > > In general the patch series seems okay to me and, as far as I'm > > concerned, if this goes in with no changes at all I would have no > > qualms. > > > > That said, I do have a number of relatively minor comments that I'll > > send in reply to individual patches. For the earlier patches in the > > series (like this one) I'm going to reply to "v2" since that's where I > > had started to write them, but I don't think anything mentioned in > > those was affected by the changes in v3. > > > > On Fri, Jul 15, 2022 at 3:24 AM Francisco Casas <fcasas(a)codeweavers.com> wrote: > >> > >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> > >> --- > >> > >> v2: > >> * Use "const struct vkd3d_shader_location *" instead of "const struct > >> vkd3d_shader_location". > >> * Removed 'in hlsl.y' in the patch subject. > >> * Use vkd3d_string_buffer for initializing the deref synthetic variable names. > >> * Move common "load = hlsl_new_load" pattern out of the if..else branches. > >> > >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> > >> --- > >> libs/vkd3d-shader/hlsl.y | 98 +++++++++++++++++++++++++++------------- > >> 1 file changed, 67 insertions(+), 31 deletions(-) > >> > >> diff --git a/libs/vkd3d-shader/hlsl.y b/libs/vkd3d-shader/hlsl.y > >> index bfafd981..f5c9f4ca 100644 > >> --- a/libs/vkd3d-shader/hlsl.y > >> +++ b/libs/vkd3d-shader/hlsl.y > >> @@ -272,8 +272,8 @@ static bool implicit_compatible_data_types(struct hlsl_type *t1, struct hlsl_typ > >> return false; > >> } > >> > >> -static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, > >> - struct hlsl_ir_node *offset, struct hlsl_type *data_type, const struct vkd3d_shader_location loc); > >> +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, > >> + unsigned int comp, const struct vkd3d_shader_location *loc); > >> > >> static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, > >> struct hlsl_ir_node *node, struct hlsl_type *dst_type, const struct vkd3d_shader_location *loc) > >> @@ -311,8 +311,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, > >> > >> for (dst_idx = 0; dst_idx < dst_type->dimx * dst_type->dimy; ++dst_idx) > >> { > >> - struct hlsl_type *src_scalar_type, *dst_scalar_type; > >> - unsigned int src_idx, src_offset, dst_offset; > >> + struct hlsl_type *dst_scalar_type; > >> + unsigned int src_idx, dst_offset; > >> struct hlsl_ir_store *store; > >> struct hlsl_ir_constant *c; > >> > >> @@ -335,13 +335,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, > >> } > >> > >> dst_offset = hlsl_compute_component_offset(ctx, dst_type, dst_idx, &dst_scalar_type); > >> - src_offset = hlsl_compute_component_offset(ctx, src_type, src_idx, &src_scalar_type); > >> - > >> - if (!(c = hlsl_new_uint_constant(ctx, src_offset, loc))) > >> - return NULL; > >> - list_add_tail(instrs, &c->node.entry); > >> > >> - if (!(load = add_load(ctx, instrs, node, &c->node, src_scalar_type, *loc))) > >> + if (!(load = add_load_component(ctx, instrs, node, src_idx, loc))) > >> return NULL; > >> > >> if (!(cast = hlsl_new_cast(ctx, &load->node, dst_scalar_type, loc))) > >> @@ -668,6 +663,62 @@ static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, > >> return load; > >> } > >> > >> +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, > >> + unsigned int comp, const struct vkd3d_shader_location *loc) > > > > I would avoid using any "node" variable name in new code. > > Understood. However, in this particular case (and later, > add_load_index()) I can't think of a better name for the node argument, > besides "value". "Instr" should always work as a replacement. Node really isn't an appropriate name anymore, specifically since we flattened the IR a while back.

Aug. 3, 2022

Re: [PATCH vkd3d 05/17] vkd3d-shader/hlsl: Introduce add_load_component().

by Francisco Casas

On 28-07-22 16:44, Matteo Bruni wrote: > Okay, I guess I managed to read the patch series through. Sorry it > took me way longer than I'd hoped, and I didn't even properly review > the individual patches (e.g. apply them and check that the tests pass > after each one). > > In general the patch series seems okay to me and, as far as I'm > concerned, if this goes in with no changes at all I would have no > qualms. > > That said, I do have a number of relatively minor comments that I'll > send in reply to individual patches. For the earlier patches in the > series (like this one) I'm going to reply to "v2" since that's where I > had started to write them, but I don't think anything mentioned in > those was affected by the changes in v3. > > On Fri, Jul 15, 2022 at 3:24 AM Francisco Casas <fcasas(a)codeweavers.com> wrote: >> >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> >> --- >> >> v2: >> * Use "const struct vkd3d_shader_location *" instead of "const struct >> vkd3d_shader_location". >> * Removed 'in hlsl.y' in the patch subject. >> * Use vkd3d_string_buffer for initializing the deref synthetic variable names. >> * Move common "load = hlsl_new_load" pattern out of the if..else branches. >> >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> >> --- >> libs/vkd3d-shader/hlsl.y | 98 +++++++++++++++++++++++++++------------- >> 1 file changed, 67 insertions(+), 31 deletions(-) >> >> diff --git a/libs/vkd3d-shader/hlsl.y b/libs/vkd3d-shader/hlsl.y >> index bfafd981..f5c9f4ca 100644 >> --- a/libs/vkd3d-shader/hlsl.y >> +++ b/libs/vkd3d-shader/hlsl.y >> @@ -272,8 +272,8 @@ static bool implicit_compatible_data_types(struct hlsl_type *t1, struct hlsl_typ >> return false; >> } >> >> -static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, >> - struct hlsl_ir_node *offset, struct hlsl_type *data_type, const struct vkd3d_shader_location loc); >> +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, >> + unsigned int comp, const struct vkd3d_shader_location *loc); >> >> static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, >> struct hlsl_ir_node *node, struct hlsl_type *dst_type, const struct vkd3d_shader_location *loc) >> @@ -311,8 +311,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, >> >> for (dst_idx = 0; dst_idx < dst_type->dimx * dst_type->dimy; ++dst_idx) >> { >> - struct hlsl_type *src_scalar_type, *dst_scalar_type; >> - unsigned int src_idx, src_offset, dst_offset; >> + struct hlsl_type *dst_scalar_type; >> + unsigned int src_idx, dst_offset; >> struct hlsl_ir_store *store; >> struct hlsl_ir_constant *c; >> >> @@ -335,13 +335,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, >> } >> >> dst_offset = hlsl_compute_component_offset(ctx, dst_type, dst_idx, &dst_scalar_type); >> - src_offset = hlsl_compute_component_offset(ctx, src_type, src_idx, &src_scalar_type); >> - >> - if (!(c = hlsl_new_uint_constant(ctx, src_offset, loc))) >> - return NULL; >> - list_add_tail(instrs, &c->node.entry); >> >> - if (!(load = add_load(ctx, instrs, node, &c->node, src_scalar_type, *loc))) >> + if (!(load = add_load_component(ctx, instrs, node, src_idx, loc))) >> return NULL; >> >> if (!(cast = hlsl_new_cast(ctx, &load->node, dst_scalar_type, loc))) >> @@ -668,6 +663,62 @@ static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, >> return load; >> } >> >> +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, >> + unsigned int comp, const struct vkd3d_shader_location *loc) > > I would avoid using any "node" variable name in new code. Understood. However, in this particular case (and later, add_load_index()) I can't think of a better name for the node argument, besides "value".

Aug. 3, 2022

Re: [PATCH 2/2] mshtml: Implement targetOrigin for postMessage.

by Marvin

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=120464 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

Aug. 3, 2022

Re: [PATCH vkd3d v3 09/17] vkd3d-shader/hlsl: Replace register offsets with index paths in load initializations.

by Zebediah Figura (she/her)

On 8/2/22 15:25, Matteo Bruni wrote: >> BTW, an alternative name for the function could be >> 'traverse_path_from_component_index', but I am not totally sure. > > Also good, it feels like an improvement to me. > > I wonder what Zeb and Giovanni think about this (if anything) :) It's good enough.

Aug. 3, 2022

Re: [PATCH 2/5] d3d9/tests: Expand tests for valid pools in UpdateTexture().

by Marvin

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=120466 Your paranoid android. === w8 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w8adm (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w864 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1507 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1809 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_tsign (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w864 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1507 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1809 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_2qxl (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. device.c:14775: Test failed: Adapter 1: Expect window rect (1024,0)-(2304,800), got (0,0)-(1280,800). === w1064_adm (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_tsign (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_en_AE_u8 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_ar (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_ja (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_zh_CN (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === debian11 (64 bit WoW report) === d3d9: device: Timeout

Aug. 3, 2022

Re: [PATCH 1/5] d3d8/tests: Expand tests for valid pools in UpdateTexture().

by Marvin

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=120465 Your paranoid android. === w1064v1507 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === w1064v1809 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === w10pro64 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === debian11 (32 bit report) === d3d8: Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b859f). === debian11 (32 bit German report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (32 bit French report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (32 bit Chinese:China report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (64 bit WoW report) === d3d8: Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000000712b2dce).

Aug. 3, 2022

Re: [PATCH 2/3] dlls/urlmon/tests: Don't use read as a global variable.

by Marvin

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=120438 Your paranoid android. === w1064v1507 (32 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064_adm (64 bit report) === urlmon: url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 === debian11 (32 bit report) === urlmon: url.c:1654: Test failed: unexpected call OnProgress_CONNECTING url.c:1466: Test failed: progress 2: status = 302

Aug. 3, 2022

Re: [PATCH 7/7] win32u: Move display placement logic out of graphics drivers.

by Marvin

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=120436 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 error: patch failed: dlls/winex11.drv/display.c:390 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 error: patch failed: dlls/winex11.drv/display.c:390 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 6/7] win32u: Use current mode position if desired mode doesn't specify it.

by Marvin

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=120435 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 5/7] win32u: Validate NtUserChangeDisplaySettings mode against available modes.

by Marvin

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=120434 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 6/6] mf: Propagate missing attributes to downstream media types.

by Marvin

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=120429 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 5/6] mf: Use the MFT_CATEGORY_VIDEO_PROCESSOR category for converters.

by Marvin

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=120428 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 4/6] winegstreamer: Better implement Video Processor MFT.

by Marvin

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=120427 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 3/6] mf/tests: Add topology loader tests with video formats.

by Marvin

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=120426 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 2/6] mf/tests: Add video processor conversion tests.

by Marvin

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=120425 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH 1/6] mf/tests: Rotate test videos 90° to better show vertical flips.

by Marvin

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=120424 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

Aug. 3, 2022

Re: [PATCH vkd3d v3 09/17] vkd3d-shader/hlsl: Replace register offsets with index paths in load initializations.

by Matteo Bruni

On Tue, Aug 2, 2022 at 9:19 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: > > Hi, Hi Francisco, big thumb up from me. I left a couple little replies in-line. > On 28-07-22 16:59, Matteo Bruni wrote: > > On Wed, Jul 20, 2022 at 3:23 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: > >> > >> The transform_deref_paths_into_offsets pass turns these index paths back > >> into register offsets. > >> > >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> > >> --- > >> > >> The idea is that we can move the transform_deref_paths_into_offsets() > >> pass forward as we translate more passes to work with index paths. > >> This, until register offsets can be totally removed, after we implement > >> the SMxIRs and their translations. > >> > >> The aim is to have 3 ways of initializing load/store nodes when using index > >> paths: > >> > >> * One that initializes the node from a another's node deref and and > >> optional index to be appended to that deref's path. > >> * One that initializes the node from a deref and the index > >> of a single basic component within it. This one also generates constant > >> nodes for the required path, so it also initializes an instruction block > >> whose instructions must be inserted in the instruction list. > >> * One that initializes the node directly for a whole variable. These functions > >> are already present: hlsl_new_var_load() and hlsl_new_simple_store(). > >> > >> The signatures of these functions are to be placed nearby in hlsl.h as > >> they are introduced in the following patches. > >> > >> It is worth noting that the use of index paths allows to remove the data type > >> argument when initializing store/loads because it can now be deducted from the > >> variable and the hlsl_deref. > >> > >> Applying an index over a matrix derefence retrieves a vector. If the matrix > >> is row_major, this corresponds to a row, otherwise, it corresponds to a > >> column. So, the code should take matrix majority into account, at least until > >> the split_matrix_copies pass. > >> > >> The first index in a path after a loading a struct should be an > >> hlsl_ir_constant, since the field that's being addressed is always > >> known at parse-time. > >> > >> hlsl_init_simple_deref_from_var() can be used to initialize a deref that can > >> be passed by reference to the load and store initialization functions. > >> This value shall not be modified after being created and does not > >> require to call hlsl_cleanup_deref(). > >> The deref obtained with this function, can also be passed be passed as prefix > >> to deref_from_component_index(). > >> > >> --- > >> > >> v3: > >> * Replaced compute_component_path() with deref_from_component_index(). > >> * Wrote implementation of init_deref() and get_type_from_deref() further > >> up in the file. > >> * Made hlsl_new_load_component() use deref_from_component_index() > >> instead of the removed compute_component_path(). > >> * Rewrote hlsl.c function comments in present and active voice. > >> * Renamed > >> typep -> type_ptr > >> indexp -> index_ptr > >> in subtype_index_from_component_index(). > >> * Added space before '?' in ternary operators. > >> > >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> > >> --- > >> libs/vkd3d-shader/hlsl.c | 298 +++++++++++++++++++++++++++++-- > >> libs/vkd3d-shader/hlsl.h | 35 +++- > >> libs/vkd3d-shader/hlsl.y | 102 ++++++----- > >> libs/vkd3d-shader/hlsl_codegen.c | 44 +++++ > >> 4 files changed, 410 insertions(+), 69 deletions(-) > >> > >> diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c > >> index 66acce23..535433ee 100644 > >> --- a/libs/vkd3d-shader/hlsl.c > >> +++ b/libs/vkd3d-shader/hlsl.c > >> @@ -330,6 +330,176 @@ unsigned int hlsl_compute_component_offset(struct hlsl_ctx *ctx, struct hlsl_typ > >> return 0; > >> } > >> > >> +static bool type_is_single_component(const struct hlsl_type *type) > >> +{ > >> + return type->type == HLSL_CLASS_SCALAR || type->type == HLSL_CLASS_OBJECT; > >> +} > >> + > >> +/* Given a type and a component index, this function returns the next path index required to reach > >> + * the component within the type. > >> + * It sets *type to the subtype within the original type that contains the component. > >> + * It sets *index to the index of the component within *type. */ > > > > Now *type_ptr and *index_ptr respectively, right? > > > > Yep. > > >> +static unsigned int subtype_index_from_component_index(struct hlsl_ctx *ctx, > >> + struct hlsl_type **type_ptr, unsigned int *index_ptr) > > > > After rereading the patch a number of times, I think the prototype is > > okay (not sure about the name, it sounds like a "get" but it does > > change the two parameters, not that I have better suggestions) but > > that comment above needs some clarification. What this function does > > is to move one step through the "path", or component index I guess, > > returning the "index" to be taken for the outer data type and updating > > type_ptr and index_ptr (which are two in/out parameters btw, their > > types do make it somewhat expected but I wouldn't say it's super > > obvious at a first glance) with the next inner type and index. > > Which I guess is what the comment is trying to convey, but dunno, it > > really didn't work for me. It might be enough to tweak it with more > > details (e.g. next -> outer?) or maybe it deserves some more > > substantial rewriting. > > > > Okay, how about: > > /* Given a type and a component index, this function moves one step > through the path required to > * reach that component within the type. > * It returns the first index of this path. > * It sets *type_ptr to the (outermost) type within the original type > that contains the component. > * It sets *index_ptr to the index of the component within *type_ptr. > * So, this function can be called several times in sequence to obtain > all the path's indexes until > * the component is finally reached. */ > > ? I like it. > BTW, an alternative name for the function could be > 'traverse_path_from_component_index', but I am not totally sure. Also good, it feels like an improvement to me. I wonder what Zeb and Giovanni think about this (if anything) :) > >> +{ > >> + struct hlsl_type *type = *type_ptr; > >> + unsigned int index = *index_ptr; > >> + > >> + assert(!type_is_single_component(type)); > >> + assert(index < hlsl_type_component_count(type)); > >> + > >> + switch (type->type) > >> + { > >> + case HLSL_CLASS_VECTOR: > >> + assert(index < type->dimx); > >> + *type_ptr = hlsl_get_scalar_type(ctx, type->base_type); > >> + *index_ptr = 0; > >> + return index; > >> + > >> + case HLSL_CLASS_MATRIX: > >> + { > >> + unsigned int y = index / type->dimx, x = index % type->dimx; > >> + bool row_major = hlsl_type_is_row_major(type); > >> + > >> + assert(index < type->dimx * type->dimy); > >> + *type_ptr = hlsl_get_vector_type(ctx, type->base_type, row_major ? type->dimx : type->dimy); > >> + *index_ptr = row_major ? x : y; > >> + return row_major ? y : x; > >> + } > >> + > >> + case HLSL_CLASS_ARRAY: > >> + { > >> + unsigned int elem_comp_count = hlsl_type_component_count(type->e.array.type); > >> + unsigned int array_index; > >> + > >> + *type_ptr = type->e.array.type; > >> + *index_ptr = index % elem_comp_count; > >> + array_index = index / elem_comp_count; > >> + assert(array_index < type->e.array.elements_count); > >> + return array_index; > >> + } > >> + > >> + case HLSL_CLASS_STRUCT: > >> + { > >> + struct hlsl_struct_field *field; > >> + unsigned int field_comp_count, i; > >> + > >> + for (i = 0; i < type->e.record.field_count; ++i) > >> + { > >> + field = &type->e.record.fields[i]; > >> + field_comp_count = hlsl_type_component_count(field->type); > >> + if (index < field_comp_count) > >> + { > >> + *type_ptr = field->type; > >> + *index_ptr = index; > >> + return i; > >> + } > >> + index -= field_comp_count; > >> + } > >> + assert(0); > >> + return 0; > >> + } > >> + > >> + default: > >> + assert(0); > >> + return 0; > >> + } > >> +} > >> + > >> +struct hlsl_type *hlsl_type_get_component_type(struct hlsl_ctx *ctx, struct hlsl_type *type, > >> + unsigned int index) > >> +{ > >> + while (!type_is_single_component(type)) > >> + subtype_index_from_component_index(ctx, &type, &index); > >> + > >> + return type; > >> +} > >> + > >> +static bool init_deref(struct hlsl_ctx *ctx, struct hlsl_deref *deref, struct hlsl_ir_var *var, > >> + unsigned int path_len) > >> +{ > >> + deref->var = var; > >> + deref->path_len = path_len; > >> + deref->offset.node = NULL; > >> + > >> + if (path_len == 0) > >> + { > >> + deref->path = NULL; > >> + return true; > >> + } > >> + > >> + if (!(deref->path = hlsl_alloc(ctx, sizeof(*deref->path) * deref->path_len))) > >> + { > >> + deref->var = NULL; > >> + deref->path_len = 0; > >> + return false; > >> + } > >> + > >> + return true; > >> +} > >> + > >> +static struct hlsl_type *get_type_from_deref(struct hlsl_ctx *ctx, const struct hlsl_deref *deref) > >> +{ > >> + struct hlsl_type *type; > >> + unsigned int i; > >> + > >> + assert(deref); > >> + assert(!deref->offset.node); > >> + > >> + type = deref->var->data_type; > >> + for (i = 0; i < deref->path_len; ++i) > >> + type = hlsl_get_type_from_path_index(ctx, type, deref->path[i].node); > >> + return type; > >> +} > >> + > >> +/* Initializes a deref from another deref (prefix) and a component index. */ > >> +static bool deref_from_component_index(struct hlsl_ctx *ctx, struct hlsl_block *block, > >> + struct hlsl_deref *deref, const struct hlsl_deref *prefix, unsigned int index, > >> + const struct vkd3d_shader_location *loc) > > > > It might come as a shock but I don't like this function's name. > > Originally these x_from_y() kind of functions were always "conversion" > > functions, i.e. take object y and return something from it as type x. > > Which I guess is technically what this function is, but I don't feel > > like that is the best way to represent it. > > > > For one, this function effectively has 2 out parameters (block and > > deref), in that it also generates instructions and adds them to the > > block list. I guess it's not any different from a few other functions > > you're introducing in the patchset but, as it is, the comment feels > > somewhat partial. I would mention "block" as another byproduct of the > > function in the comment at the top. > > > > Okay, I will write it as: > > /* Initializes a deref from another deref (prefix) and a component index. > * *block is initialized to contain the new constant node instructions > used by the deref's path. */ > > > In regard to the name, maybe just adding a new_ (or create_? > > generate_? init_?) in front would be enough. I don't have great > > suggestions, as usual. > > > > I am for the "init_" prefix. > > > Somewhat minor, and probably more controversial, but maybe still worth > > mentioning: instead of returning a bool, the function could return a > > pointer to the deref. It should return NULL in the codepaths currently > > returning "false", to maintain the current semantics (which are fine). > > While it's unlikely that the return value is going to be super useful, > > making this function resemble the other similar ones introduced in > > this patch and previously has value in my mind. Also, of course, that > > doesn't mean you can drop the "deref" parameter. > > > > Hmm, while the other functions return pointers to nodes (or to a > specific type of node) we never return derefs. > > Personally, when I see an initialization function that returns a > pointer, my first inclination is to think that said function allocates > memory, which isn't the case for derefs, which are most of time > contained in other structs (hlsl_ir_store, hlsl_ir_load, or > hlsl_ir_resource_load) and are never allocated separately. Yes, that's a fair point. > > >> +{ > >> + unsigned int path_len, path_index, deref_path_len, i; > >> + struct hlsl_type *path_type; > >> + struct hlsl_ir_constant *c; > >> + > >> + list_init(&block->instrs); > >> + > >> + path_len = 0; > >> + path_type = get_type_from_deref(ctx, prefix); > >> + path_index = index; > >> + while (!type_is_single_component(path_type)) > >> + { > >> + subtype_index_from_component_index(ctx, &path_type, &path_index); > >> + ++path_len; > >> + } > >> + > >> + if (!init_deref(ctx, deref, prefix->var, prefix->path_len + path_len)) > >> + return false; > >> + > >> + deref_path_len = 0; > >> + for (i = 0; i < prefix->path_len; ++i) > >> + hlsl_src_from_node(&deref->path[deref_path_len++], prefix->path[i].node); > >> + > >> + path_type = get_type_from_deref(ctx, prefix); > >> + path_index = index; > >> + while (!type_is_single_component(path_type)) > >> + { > >> + unsigned int next_index = subtype_index_from_component_index(ctx, &path_type, &path_index); > >> + > >> + if (!(c = hlsl_new_uint_constant(ctx, next_index, loc))) > >> + { > >> + hlsl_free_instr_list(&block->instrs); > >> + return false; > >> + } > >> + list_add_tail(&block->instrs, &c->node.entry); > >> + > >> + hlsl_src_from_node(&deref->path[deref_path_len++], &c->node); > >> + } > >> + > >> + assert(deref_path_len == deref->path_len); > >> + > >> + return true; > >> +} > >> + > >> struct hlsl_type *hlsl_get_type_from_path_index(struct hlsl_ctx *ctx, const struct hlsl_type *type, > >> struct hlsl_ir_node *node) > >> { > >> @@ -435,6 +605,37 @@ struct hlsl_ir_node *hlsl_new_offset_from_path_index(struct hlsl_ctx *ctx, struc > >> return idx_offset; > >> } > >> > >> +struct hlsl_ir_node *hlsl_new_offset_node_from_deref(struct hlsl_ctx *ctx, struct hlsl_block *block, > >> + const struct hlsl_deref *deref, const struct vkd3d_shader_location *loc) > > > > For reference, I find the naming of this one okay (aside from node -> > > instr or something), probably just because of the new_ prefix. > > It makes sense to me to keep a distinction between 'new_' and 'init_' > when the new value's memory is allocated in the function or not. > > Ok, I will rename it to 'hlsl_new_offset_instr_from_deref'.

Aug. 2, 2022

Re: [PATCH vkd3d v3 09/17] vkd3d-shader/hlsl: Replace register offsets with index paths in load initializations.

by Francisco Casas

Hi, On 28-07-22 16:59, Matteo Bruni wrote: > On Wed, Jul 20, 2022 at 3:23 PM Francisco Casas <fcasas(a)codeweavers.com> wrote: >> >> The transform_deref_paths_into_offsets pass turns these index paths back >> into register offsets. >> >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> >> --- >> >> The idea is that we can move the transform_deref_paths_into_offsets() >> pass forward as we translate more passes to work with index paths. >> This, until register offsets can be totally removed, after we implement >> the SMxIRs and their translations. >> >> The aim is to have 3 ways of initializing load/store nodes when using index >> paths: >> >> * One that initializes the node from a another's node deref and and >> optional index to be appended to that deref's path. >> * One that initializes the node from a deref and the index >> of a single basic component within it. This one also generates constant >> nodes for the required path, so it also initializes an instruction block >> whose instructions must be inserted in the instruction list. >> * One that initializes the node directly for a whole variable. These functions >> are already present: hlsl_new_var_load() and hlsl_new_simple_store(). >> >> The signatures of these functions are to be placed nearby in hlsl.h as >> they are introduced in the following patches. >> >> It is worth noting that the use of index paths allows to remove the data type >> argument when initializing store/loads because it can now be deducted from the >> variable and the hlsl_deref. >> >> Applying an index over a matrix derefence retrieves a vector. If the matrix >> is row_major, this corresponds to a row, otherwise, it corresponds to a >> column. So, the code should take matrix majority into account, at least until >> the split_matrix_copies pass. >> >> The first index in a path after a loading a struct should be an >> hlsl_ir_constant, since the field that's being addressed is always >> known at parse-time. >> >> hlsl_init_simple_deref_from_var() can be used to initialize a deref that can >> be passed by reference to the load and store initialization functions. >> This value shall not be modified after being created and does not >> require to call hlsl_cleanup_deref(). >> The deref obtained with this function, can also be passed be passed as prefix >> to deref_from_component_index(). >> >> --- >> >> v3: >> * Replaced compute_component_path() with deref_from_component_index(). >> * Wrote implementation of init_deref() and get_type_from_deref() further >> up in the file. >> * Made hlsl_new_load_component() use deref_from_component_index() >> instead of the removed compute_component_path(). >> * Rewrote hlsl.c function comments in present and active voice. >> * Renamed >> typep -> type_ptr >> indexp -> index_ptr >> in subtype_index_from_component_index(). >> * Added space before '?' in ternary operators. >> >> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> >> --- >> libs/vkd3d-shader/hlsl.c | 298 +++++++++++++++++++++++++++++-- >> libs/vkd3d-shader/hlsl.h | 35 +++- >> libs/vkd3d-shader/hlsl.y | 102 ++++++----- >> libs/vkd3d-shader/hlsl_codegen.c | 44 +++++ >> 4 files changed, 410 insertions(+), 69 deletions(-) >> >> diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c >> index 66acce23..535433ee 100644 >> --- a/libs/vkd3d-shader/hlsl.c >> +++ b/libs/vkd3d-shader/hlsl.c >> @@ -330,6 +330,176 @@ unsigned int hlsl_compute_component_offset(struct hlsl_ctx *ctx, struct hlsl_typ >> return 0; >> } >> >> +static bool type_is_single_component(const struct hlsl_type *type) >> +{ >> + return type->type == HLSL_CLASS_SCALAR || type->type == HLSL_CLASS_OBJECT; >> +} >> + >> +/* Given a type and a component index, this function returns the next path index required to reach >> + * the component within the type. >> + * It sets *type to the subtype within the original type that contains the component. >> + * It sets *index to the index of the component within *type. */ > > Now *type_ptr and *index_ptr respectively, right? > Yep. >> +static unsigned int subtype_index_from_component_index(struct hlsl_ctx *ctx, >> + struct hlsl_type **type_ptr, unsigned int *index_ptr) > > After rereading the patch a number of times, I think the prototype is > okay (not sure about the name, it sounds like a "get" but it does > change the two parameters, not that I have better suggestions) but > that comment above needs some clarification. What this function does > is to move one step through the "path", or component index I guess, > returning the "index" to be taken for the outer data type and updating > type_ptr and index_ptr (which are two in/out parameters btw, their > types do make it somewhat expected but I wouldn't say it's super > obvious at a first glance) with the next inner type and index. > Which I guess is what the comment is trying to convey, but dunno, it > really didn't work for me. It might be enough to tweak it with more > details (e.g. next -> outer?) or maybe it deserves some more > substantial rewriting. > Okay, how about: /* Given a type and a component index, this function moves one step through the path required to * reach that component within the type. * It returns the first index of this path. * It sets *type_ptr to the (outermost) type within the original type that contains the component. * It sets *index_ptr to the index of the component within *type_ptr. * So, this function can be called several times in sequence to obtain all the path's indexes until * the component is finally reached. */ ? BTW, an alternative name for the function could be 'traverse_path_from_component_index', but I am not totally sure. >> +{ >> + struct hlsl_type *type = *type_ptr; >> + unsigned int index = *index_ptr; >> + >> + assert(!type_is_single_component(type)); >> + assert(index < hlsl_type_component_count(type)); >> + >> + switch (type->type) >> + { >> + case HLSL_CLASS_VECTOR: >> + assert(index < type->dimx); >> + *type_ptr = hlsl_get_scalar_type(ctx, type->base_type); >> + *index_ptr = 0; >> + return index; >> + >> + case HLSL_CLASS_MATRIX: >> + { >> + unsigned int y = index / type->dimx, x = index % type->dimx; >> + bool row_major = hlsl_type_is_row_major(type); >> + >> + assert(index < type->dimx * type->dimy); >> + *type_ptr = hlsl_get_vector_type(ctx, type->base_type, row_major ? type->dimx : type->dimy); >> + *index_ptr = row_major ? x : y; >> + return row_major ? y : x; >> + } >> + >> + case HLSL_CLASS_ARRAY: >> + { >> + unsigned int elem_comp_count = hlsl_type_component_count(type->e.array.type); >> + unsigned int array_index; >> + >> + *type_ptr = type->e.array.type; >> + *index_ptr = index % elem_comp_count; >> + array_index = index / elem_comp_count; >> + assert(array_index < type->e.array.elements_count); >> + return array_index; >> + } >> + >> + case HLSL_CLASS_STRUCT: >> + { >> + struct hlsl_struct_field *field; >> + unsigned int field_comp_count, i; >> + >> + for (i = 0; i < type->e.record.field_count; ++i) >> + { >> + field = &type->e.record.fields[i]; >> + field_comp_count = hlsl_type_component_count(field->type); >> + if (index < field_comp_count) >> + { >> + *type_ptr = field->type; >> + *index_ptr = index; >> + return i; >> + } >> + index -= field_comp_count; >> + } >> + assert(0); >> + return 0; >> + } >> + >> + default: >> + assert(0); >> + return 0; >> + } >> +} >> + >> +struct hlsl_type *hlsl_type_get_component_type(struct hlsl_ctx *ctx, struct hlsl_type *type, >> + unsigned int index) >> +{ >> + while (!type_is_single_component(type)) >> + subtype_index_from_component_index(ctx, &type, &index); >> + >> + return type; >> +} >> + >> +static bool init_deref(struct hlsl_ctx *ctx, struct hlsl_deref *deref, struct hlsl_ir_var *var, >> + unsigned int path_len) >> +{ >> + deref->var = var; >> + deref->path_len = path_len; >> + deref->offset.node = NULL; >> + >> + if (path_len == 0) >> + { >> + deref->path = NULL; >> + return true; >> + } >> + >> + if (!(deref->path = hlsl_alloc(ctx, sizeof(*deref->path) * deref->path_len))) >> + { >> + deref->var = NULL; >> + deref->path_len = 0; >> + return false; >> + } >> + >> + return true; >> +} >> + >> +static struct hlsl_type *get_type_from_deref(struct hlsl_ctx *ctx, const struct hlsl_deref *deref) >> +{ >> + struct hlsl_type *type; >> + unsigned int i; >> + >> + assert(deref); >> + assert(!deref->offset.node); >> + >> + type = deref->var->data_type; >> + for (i = 0; i < deref->path_len; ++i) >> + type = hlsl_get_type_from_path_index(ctx, type, deref->path[i].node); >> + return type; >> +} >> + >> +/* Initializes a deref from another deref (prefix) and a component index. */ >> +static bool deref_from_component_index(struct hlsl_ctx *ctx, struct hlsl_block *block, >> + struct hlsl_deref *deref, const struct hlsl_deref *prefix, unsigned int index, >> + const struct vkd3d_shader_location *loc) > > It might come as a shock but I don't like this function's name. > Originally these x_from_y() kind of functions were always "conversion" > functions, i.e. take object y and return something from it as type x. > Which I guess is technically what this function is, but I don't feel > like that is the best way to represent it. > > For one, this function effectively has 2 out parameters (block and > deref), in that it also generates instructions and adds them to the > block list. I guess it's not any different from a few other functions > you're introducing in the patchset but, as it is, the comment feels > somewhat partial. I would mention "block" as another byproduct of the > function in the comment at the top. > Okay, I will write it as: /* Initializes a deref from another deref (prefix) and a component index. * *block is initialized to contain the new constant node instructions used by the deref's path. */ > In regard to the name, maybe just adding a new_ (or create_? > generate_? init_?) in front would be enough. I don't have great > suggestions, as usual. > I am for the "init_" prefix. > Somewhat minor, and probably more controversial, but maybe still worth > mentioning: instead of returning a bool, the function could return a > pointer to the deref. It should return NULL in the codepaths currently > returning "false", to maintain the current semantics (which are fine). > While it's unlikely that the return value is going to be super useful, > making this function resemble the other similar ones introduced in > this patch and previously has value in my mind. Also, of course, that > doesn't mean you can drop the "deref" parameter. > Hmm, while the other functions return pointers to nodes (or to a specific type of node) we never return derefs. Personally, when I see an initialization function that returns a pointer, my first inclination is to think that said function allocates memory, which isn't the case for derefs, which are most of time contained in other structs (hlsl_ir_store, hlsl_ir_load, or hlsl_ir_resource_load) and are never allocated separately. >> +{ >> + unsigned int path_len, path_index, deref_path_len, i; >> + struct hlsl_type *path_type; >> + struct hlsl_ir_constant *c; >> + >> + list_init(&block->instrs); >> + >> + path_len = 0; >> + path_type = get_type_from_deref(ctx, prefix); >> + path_index = index; >> + while (!type_is_single_component(path_type)) >> + { >> + subtype_index_from_component_index(ctx, &path_type, &path_index); >> + ++path_len; >> + } >> + >> + if (!init_deref(ctx, deref, prefix->var, prefix->path_len + path_len)) >> + return false; >> + >> + deref_path_len = 0; >> + for (i = 0; i < prefix->path_len; ++i) >> + hlsl_src_from_node(&deref->path[deref_path_len++], prefix->path[i].node); >> + >> + path_type = get_type_from_deref(ctx, prefix); >> + path_index = index; >> + while (!type_is_single_component(path_type)) >> + { >> + unsigned int next_index = subtype_index_from_component_index(ctx, &path_type, &path_index); >> + >> + if (!(c = hlsl_new_uint_constant(ctx, next_index, loc))) >> + { >> + hlsl_free_instr_list(&block->instrs); >> + return false; >> + } >> + list_add_tail(&block->instrs, &c->node.entry); >> + >> + hlsl_src_from_node(&deref->path[deref_path_len++], &c->node); >> + } >> + >> + assert(deref_path_len == deref->path_len); >> + >> + return true; >> +} >> + >> struct hlsl_type *hlsl_get_type_from_path_index(struct hlsl_ctx *ctx, const struct hlsl_type *type, >> struct hlsl_ir_node *node) >> { >> @@ -435,6 +605,37 @@ struct hlsl_ir_node *hlsl_new_offset_from_path_index(struct hlsl_ctx *ctx, struc >> return idx_offset; >> } >> >> +struct hlsl_ir_node *hlsl_new_offset_node_from_deref(struct hlsl_ctx *ctx, struct hlsl_block *block, >> + const struct hlsl_deref *deref, const struct vkd3d_shader_location *loc) > > For reference, I find the naming of this one okay (aside from node -> > instr or something), probably just because of the new_ prefix. It makes sense to me to keep a distinction between 'new_' and 'init_' when the new value's memory is allocated in the function or not. Ok, I will rename it to 'hlsl_new_offset_instr_from_deref'.

Aug. 2, 2022

Re: [PATCH v15 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D

by Marvin

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=120358 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

Aug. 2, 2022

Re: [PATCH v14 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D

by Marvin

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=120357 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

Aug. 2, 2022

Re: [PATCH v12 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D

by Marvin

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=120356 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

Aug. 2, 2022

Re: [PATCH v11 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D

by Marvin

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=120355 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === debian11 (32 bit report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

Aug. 2, 2022

Re: [PATCH v10 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D

by Marvin

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=120354 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

Aug. 2, 2022

Re: [PATCH v9 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) Dl

by Marvin

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=120351 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127.

Aug. 2, 2022

Re: [PATCH v2 4/7] ws2_32/tests: Work around a Linux bug.

by Marvin

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=120345 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8699: Test failed: got 0

Aug. 2, 2022

Re: [PATCH v2 3/7] ws2_32/tests: Test send() after TCP reset.

by Marvin

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=120344 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

Aug. 2, 2022

Re: [PATCH v2 1/7] ws2_32/tests: Test sending data to a peer is closed().

by Marvin

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=120342 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

Aug. 2, 2022

Re: [PATCH v6 3/3] cabinet: Implement GetDllVersion implement GetDllVersion, use DllGetVersion as helper function to retreiv

by Marvin

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=120332 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

Aug. 1, 2022

Re: [PATCH v6 2/3] cabinet: implement DllGetVersion correctly implement DllGetVersion with correct parameter and behaviour c

by Marvin

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=120331 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

Aug. 1, 2022

Re: [PATCH v6 1/3] cabinet: test GetDllVersion & DllGetVersion Tests are expected to fail as: DllGetVersion isn't implemente

by Marvin

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=120330 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

Aug. 1, 2022

Re: [PATCH 3/3] mshtml: Implement MediaQueryList's matches prop.

by Marvin

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=120307 Your paranoid android. === w1064v1809 (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

Aug. 1, 2022

Re: [PATCH 2/3] mshtml: Implement MediaQueryList's media prop.

by Marvin

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=120306 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

Aug. 1, 2022

Re: [PATCH 6/6] widl: Use a struct list for the import stack.

by Marvin

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=120323 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

Aug. 1, 2022