Re: [4/5] gdiplus: Add some tests for GdipGetPropertyItemSize and GdipGetPropertyItem. Take 2.

[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
http://testbot.winehq.org/JobDetails.pl?Key=19625

Your paranoid android.


=== W7PROX64 (64 bit image) ===
image.c:2817: Test failed:  0: expected property size 17 or 36, got 44
image.c:2817: Test failed:  2: expected property size 144 or 0, got 152
image.c:2817: Test failed:  3: expected property size 20 or 0, got 28

=== TEST64_W7SP1 (64 bit image) ===
image.c:2817: Test failed:  0: expected property size 17 or 36, got 44
image.c:2817: Test failed:  2: expected property size 144 or 0, got 152
image.c:2817: Test failed:  3: expected property size 20 or 0, got 28

[4/5] gdiplus: Add some tests for GdipGetPropertyItemSize and GdipGetPropertyItem. Take 2.

[Dmitry Timoshkov]

Marvin <testbot(a)testbot.winehq.org> wrote:
> === W7PROX64 (64 bit image) ===
> image.c:2817: Test failed:  0: expected property size 17 or 36, got 44
> image.c:2817: Test failed:  2: expected property size 144 or 0, got 152
> image.c:2817: Test failed:  3: expected property size 20 or 0, got 28
>
> === TEST64_W7SP1 (64 bit image) ===
> image.c:2817: Test failed:  0: expected property size 17 or 36, got 44
> image.c:2817: Test failed:  2: expected property size 144 or 0, got 152
> image.c:2817: Test failed:  3: expected property size 20 or 0, got 28

That's a propblem with 32 and 64-bit PropertyItem structure size difference,
I sent another version of the patch.

-- 
Dmitry.