[PATCH 4/4] ncrypt/tests: Test for NCryptSetProperty

Bernhard Kölbl besentv at gmail.com
Fri Feb 18 02:33:53 CST 2022


You can use the "broken" macro to mark things as not working under certain
circumstances. It's used quite a lot in other tests, so there are plenty
examples on how to use it.

Bernhard

Santino Mazza <mazzasantino1206 at gmail.com> schrieb am Fr., 18. Feb. 2022,
01:48:

> What should I do here? It just fails on the Windows 7 machine.
>
> El jue, 17 feb 2022 a la(s) 21:00, Marvin (testbot at winehq.org) escribió:
>
>> Hi,
>>
>> While running your changed tests, I think I found new failures.
>> Being a bot and all I'm not very good at pattern recognition, so I might
>> be
>> wrong, but could you please double-check?
>>
>> Full results can be found at:
>> https://testbot.winehq.org/JobDetails.pl?Key=108414
>>
>> Your paranoid android.
>>
>>
>> === w7u_2qxl (32 bit report) ===
>>
>> ncrypt:
>> ncrypt.c:222: Test failed: got 0x80090026
>> ncrypt.c:273: Test failed: got 0x80090020
>>
>> === w7u_adm (32 bit report) ===
>>
>> ncrypt:
>> ncrypt.c:222: Test failed: got 0x80090026
>> ncrypt.c:273: Test failed: got 0x80090020
>>
>> === w7u_el (32 bit report) ===
>>
>> ncrypt:
>> ncrypt.c:222: Test failed: got 0x80090026
>> ncrypt.c:273: Test failed: got 0x80090020
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20220218/2a10a046/attachment.htm>


More information about the wine-devel mailing list