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=27623
Your paranoid android.
=== w1064 (32 bit ddraw2) ===
ddraw2.c:2391: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw2) ===
ddraw2.c:2391: Test failed: Expected (0,0)-(512,384), got (…
[View More]0,0)-(1024,768).
=== w1064 (32 bit ddraw1) ===
ddraw1.c:2240: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw1) ===
ddraw1.c:2240: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (32 bit ddraw4) ===
ddraw4.c:2546: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw4) ===
ddraw4.c:2546: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (32 bit ddraw7) ===
ddraw7.c:2272: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw7) ===
ddraw7.c:2272: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
[View Less]
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=27612
Your paranoid android.
=== w7pro64 (32 bit device) ===
device.c:1445: Test failed: SetFullscreenState failed, hr 0x887a0004.
On 6 January 2017 at 08:07, Alex Henrie <alexhenrie24(a)gmail.com> wrote:
> Fixes https://bugs.winehq.org/show_bug.cgi?id=42159
>
This isn't a regression, right?
> @@ -2975,10 +2975,7 @@ static HRESULT WINAPI ddraw1_CreateSurface(IDirectDraw *iface,
> hr = ddraw_surface_create(ddraw, &surface_desc2, &impl, outer_unknown, 1);
> wined3d_mutex_unlock();
> if (FAILED(hr))
> - {
> - *surface = NULL;
> return hr;
> - }
…
[View More]This does a bit more than the commit message says it does, this
doesn't write to *surface on any error from ddraw_surface_create().
That may very well be correct, but that's not what the test tests. The
test only tests that CreateSurface() doesn't crash on error with an
invalid "surface" pointer, but that could also be because of e.g. an
exception handler. If you want to prove that it doesn't (try to) write
to the "surface" pointer, you should pass a valid pointer to
CreateSurface() and test that it isn't modified after the call.
[View Less]
2017-01-06 0:07 GMT-07:00 Alex Henrie <alexhenrie24(a)gmail.com>:
> Fixes https://bugs.winehq.org/show_bug.cgi?id=42159
>
> With this patch, Sega Bug shows its intro logos, although it crashes
> with "Unhandled privileged instruction" immediately after that.
In case anyone is curious, I got rid of the "Unhandled privileged
instruction" error by modifying my ioperm wrapper described at
https://www.winehq.org/pipermail/wine-devel/2016-September/114873.html
to open ports 3D0-…
[View More]3DF.
With the patch and the ioperm wrapper, the game does not crash and the
sound plays, but the game window is all black and the console repeats
"fixme:d3d:surface_cpu_blt Filter WINED3D_TEXF_LINEAR not supported in
software blit."
-Alex
[View Less]
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=27599
Your paranoid android.
=== w1064 (32 bit ddraw7) ===
ddraw7.c:2276: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw7) ===
ddraw7.c:2276: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
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=27598
Your paranoid android.
=== w1064 (32 bit ddraw4) ===
ddraw4.c:2550: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw4) ===
ddraw4.c:2550: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
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=27597
Your paranoid android.
=== w1064 (32 bit ddraw2) ===
ddraw2.c:2395: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).
=== w1064 (64 bit ddraw2) ===
ddraw2.c:2395: Test failed: Expected (0,0)-(512,384), got (0,0)-(1024,768).