Re: crypt32/tests(5/10): Test the base and SSL policies against a certificate with an invalid critical extension

Hi,

While running your changed tests on Windows, 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
http://testbot.winehq.org/JobDetails.pl?Key=5870

Your paranoid android.

=== W98SE (32 bit chain) ===
chain.c:4113: Test failed: #0001[0]: expected 800b0101, got 800b0102
chain.c:4105: Test failed: #0001[0]: expected 800b0105, got 800b0102
chain.c:2752: Test failed: Chain 31: expected error 00000001, got 00000003. 00000020 is expected if no valid Verisign root certificate is available.
chain.c:2674: Test failed: Chain 31, element [0,1]: expected error 00000000, got 00000002. 00000020 is expected if no valid Verisign root certificate is available.
chain.c:2674: Test failed: Chain 31, element [0,2]: expected error 00000000, got 00000001. 00000020 is expected if no valid Verisign root certificate is available.
chain.c:2752: Test failed: Chain 32: expected error 00000001, got 00010001. 00000020 is expected if no valid Verisign root certificate is available.
chain.c:2712: Test failed: Chain 32: expected 3 elements, got 2

=== WNT4WSSP6 (32 bit chain) ===
chain.c:4105: Test failed: #0001[0]: expected 800b0105, got 800b0102