On 04/06/18 04:02, Huw Davies wrote:
On Sun, Jun 03, 2018 at 02:51:11PM -0500, Zebediah Figura wrote:
On 03/06/18 13:58, Marvin wrote:
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=38913
Your paranoid android.
=== wvistau64 (64 bit typelib) === typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4 typelib.c:4733: Test failed: typeattr->cbAlignment expected 8 got 4
These failures are shortcomings in widl exposed by these patches; they are fixed in patch 4/4.
You'll probably have to merge some of the patches in this series to avoid test failures at intermediate stages.
Huw.
Thanks; I'll resend it with the widl and oleaut32 patches merged.