Re: rsaenh/tests: Don't initialize the environment, the tests that follow do that.

[Marvin]

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
https://testbot.winehq.org/JobDetails.pl?Key=26484

Your paranoid android.


=== w864 (32 bit rsaenh) ===
rsaenh.c:2804: Test failed: 80090020

=== w1064 (32 bit rsaenh) ===
rsaenh.c:2804: Test failed: 80090020

=== w1064 (64 bit rsaenh) ===
rsaenh.c:2804: Test failed: 80090020

rsaenh/tests: Don't initialize the environment, the tests that follow do that.

[Huw Davies]

On 7 Nov 2016, at 13:10, Marvin <testbot(a)winehq.org> wrote:
> 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
> https://testbot.winehq.org/JobDetails.pl?Key=26484
>
> Your paranoid android.
>
> === w864 (32 bit rsaenh) ===
> rsaenh.c:2804: Test failed: 80090020
>
> === w1064 (32 bit rsaenh) ===
> rsaenh.c:2804: Test failed: 80090020
>
> === w1064 (64 bit rsaenh) ===
> rsaenh.c:2804: Test failed: 80090020

These are existing failures.

It looks like they’ve tried to stop folks using the CryptoAPI to do TLS.
I’ll probably just mark these as broken unless someone has any better ideas.

Huw.

rsaenh/tests: Don't initialize the environment, the tests that follow do that.

[Bruno Jesus]

On Mon, Nov 7, 2016 at 11:55 AM, Huw Davies <huw(a)codeweavers.com> wrote:
> > === w864 (32 bit rsaenh) ===
> > rsaenh.c:2804: Test failed: 80090020
> >
> > === w1064 (32 bit rsaenh) ===
> > rsaenh.c:2804: Test failed: 80090020
> >
> > === w1064 (64 bit rsaenh) ===
> > rsaenh.c:2804: Test failed: 80090020
>
> These are existing failures.
>
> It looks like they’ve tried to stop folks using the CryptoAPI to do TLS.
> I’ll probably just mark these as broken unless someone has any better ideas.

There is nothing we can do IMO, for unknown reasons MS broke many
different crypto DLL's starting on Windows 8. And we are not alone, at
least 1 other person has the problem:

http://stackoverflow.com/questions/28004597/cannot-create-master-hash-on-win...

rsaenh/tests: Don't initialize the environment, the tests that follow do that.

[Huw Davies]

> On 7 Nov 2016, at 15:38, Bruno Jesus <00cpxxx(a)gmail.com> wrote:
>
> On Mon, Nov 7, 2016 at 11:55 AM, Huw Davies <huw(a)codeweavers.com> wrote:
> > > === w864 (32 bit rsaenh) ===
> > > rsaenh.c:2804: Test failed: 80090020
> > >
> > > === w1064 (32 bit rsaenh) ===
> > > rsaenh.c:2804: Test failed: 80090020
> > >
> > > === w1064 (64 bit rsaenh) ===
> > > rsaenh.c:2804: Test failed: 80090020
> >
> > These are existing failures.
> >
> > It looks like they’ve tried to stop folks using the CryptoAPI to do TLS.
> > I’ll probably just mark these as broken unless someone has any better ideas.
>
> There is nothing we can do IMO, for unknown reasons MS broke many
> different crypto DLL's starting on Windows 8. And we are not alone, at
> least 1 other person has the problem:
>
> http://stackoverflow.com/questions/28004597/cannot-create-master-hash-on-win...

Yes, he also asked us:
https://forum.winehq.org/viewtopic.php?f=2&t=23773

I’ve sent in a patch to mark this as broken.

Thanks,
Huw.