[PATCH 4/7] ddraw/tests: Use flags to indicate broken render-target tests. (original) (raw)
Marvin testbot at winehq.org
Fri Dec 13 02:50:26 CST 2019
- Previous message (by thread): [PATCH 4/7] ddraw/tests: Use flags to indicate broken render-target tests.
- Next message (by thread): [PATCH 5/7] ddraw/tests: Avoid reference leaks in render-target tests.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
While running your changed tests, 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=62119
Your paranoid android.
=== w1064v1507 (32 bit report) ===
ddraw: 0c9c:ddraw2: unhandled exception c0000005 at 730B7F2E
=== w1064v1809 (32 bit report) ===
ddraw: ddraw4.c:15936: Test failed: WM_KILLFOCUS was not received. ddraw4.c:16113: Test failed: Got unexpected hr 0x887600e1. ddraw4.c:16116: Test failed: Got unexpected hr 0x887600ff. 1984:ddraw4: unhandled exception c0000005 at 00489FAF
=== w864 (64 bit report) ===
ddraw: ddraw7.c:3135: Test failed: Failed to create surface, hr 0x887601c2. 0c20:ddraw7: unhandled exception c0000005 at 00000000004EC418
- Previous message (by thread): [PATCH 4/7] ddraw/tests: Use flags to indicate broken render-target tests.
- Next message (by thread): [PATCH 5/7] ddraw/tests: Avoid reference leaks in render-target tests.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]