[PATCH] kernel32/tests: Be explicit about LoadLibraryEx() NT6+ flags
Signed-off-by: Serge Gautherie <winehq-git_serge_180711(a)gautherie.fr> --- Mostly interesting for ReactOS. --- dlls/kernel32/tests/loader.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dlls/kernel32/tests/loader.c b/dlls/kernel32/tests/loader.c index 3307382..4238f0b 100644 --- a/dlls/kernel32/tests/loader.c +++ b/dlls/kernel32/tests/loader.c @@ -1054,7 +1054,7 @@ static void test_Loader(void) if (!((ULONG_PTR)hlib_as_data_file & 3) || /* winxp */ (!hlib_as_data_file && GetLastError() == ERROR_INVALID_PARAMETER)) /* w2k3 */ { - win_skip( "LOAD_LIBRARY_AS_DATAFILE_EXCLUSIVE not supported\n" ); + win_skip("NT6+ LOAD_LIBRARY_AS_DATAFILE_EXCLUSIVE not supported\n"); FreeLibrary(hlib_as_data_file); } else @@ -1082,7 +1082,7 @@ static void test_Loader(void) if (!((ULONG_PTR)hlib_as_data_file & 3) || /* winxp */ (!hlib_as_data_file && GetLastError() == ERROR_INVALID_PARAMETER)) /* w2k3 */ { - win_skip( "LOAD_LIBRARY_AS_IMAGE_RESOURCE not supported\n" ); + win_skip("NT6+ LOAD_LIBRARY_AS_IMAGE_RESOURCE not supported\n"); FreeLibrary(hlib_as_data_file); } else -- 2.10.0.windows.1
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=78652 Your paranoid android. === w1064v1809 (32 bit report) === kernel32: loader.c:708: Test failed: 1196: wrong status c000011b/c0000130 loader.c:708: Test failed: 1201: wrong status c000011b/c0000130 loader.c:708: Test failed: 1206: wrong status c000011b/c000007b loader.c:708: Test failed: 1211: wrong status c000011b/c000007b loader.c:708: Test failed: 1216: wrong status c000011b/c000007b loader.c:708: Test failed: 1221: wrong status c000011b/c000007b loader.c:708: Test failed: 1226: wrong status c000011b/c000007b loader.c:708: Test failed: 1242: wrong status c000011b/0 loader.c:708: Test failed: 1246: wrong status c000011b/0 loader.c:708: Test failed: 1251: wrong status c000011b/0 loader.c:708: Test failed: 1255: wrong status c000011b/0 loader.c:708: Test failed: 1259: wrong status c000011b/0 loader.c:708: Test failed: 1298: wrong status c000011b/c000007b loader.c:708: Test failed: 1307: wrong status c000011b/c000007b loader.c:708: Test failed: 1312: wrong status c000011b/0 loader.c:711: Test failed: 1312: failed with c000011b expected fallback loader.c:708: Test failed: 1319: wrong status c000011b/0 loader.c:711: Test failed: 1319: failed with c000011b expected fallback loader.c:708: Test failed: 1326: wrong status c000011b/0 loader.c:711: Test failed: 1326: failed with c000011b expected fallback loader.c:708: Test failed: 1334: wrong status c000011b/0 loader.c:711: Test failed: 1334: failed with c000011b expected fallback loader.c:708: Test failed: 1341: wrong status c000011b/0 loader.c:711: Test failed: 1341: failed with c000011b expected fallback loader.c:708: Test failed: 1351: wrong status c000011b/0 loader.c:708: Test failed: 1356: wrong status c000011b/0 loader.c:708: Test failed: 1361: wrong status c000011b/0 loader.c:708: Test failed: 1366: wrong status c000011b/0 loader.c:708: Test failed: 1371: wrong status c000011b/0 === w10pro64_ar (32 bit report) === kernel32: loader.c:2764: Test failed: attached thread count should be 2 === w10pro64_he (32 bit report) === kernel32: loader.c:708: Test failed: 1206: wrong status c0000130/c000007b loader.c:708: Test failed: 1211: wrong status c0000130/c000007b loader.c:708: Test failed: 1216: wrong status c0000130/c000007b loader.c:708: Test failed: 1221: wrong status c0000130/c000007b loader.c:708: Test failed: 1226: wrong status c0000130/c000007b loader.c:708: Test failed: 1242: wrong status c0000130/0 loader.c:708: Test failed: 1246: wrong status c0000130/0 loader.c:708: Test failed: 1251: wrong status c0000130/0 loader.c:708: Test failed: 1255: wrong status c0000130/0 loader.c:708: Test failed: 1259: wrong status c0000130/0 loader.c:708: Test failed: 1298: wrong status c0000130/c000007b loader.c:708: Test failed: 1307: wrong status c0000130/c000007b loader.c:708: Test failed: 1312: wrong status c0000130/0 loader.c:711: Test failed: 1312: failed with c0000130 expected fallback loader.c:708: Test failed: 1319: wrong status c0000130/0 loader.c:711: Test failed: 1319: failed with c0000130 expected fallback loader.c:708: Test failed: 1326: wrong status c0000130/0 loader.c:711: Test failed: 1326: failed with c0000130 expected fallback loader.c:708: Test failed: 1334: wrong status c0000130/0 loader.c:711: Test failed: 1334: failed with c0000130 expected fallback loader.c:708: Test failed: 1341: wrong status c0000130/0 loader.c:711: Test failed: 1341: failed with c0000130 expected fallback loader.c:708: Test failed: 1351: wrong status c0000130/0 loader.c:708: Test failed: 1356: wrong status c0000130/0 loader.c:708: Test failed: 1361: wrong status c0000130/0 loader.c:708: Test failed: 1366: wrong status c0000130/0 loader.c:708: Test failed: 1371: wrong status c0000130/0 === w10pro64_ja (32 bit report) === kernel32: loader.c:2764: Test failed: attached thread count should be 2 === w1064v1809 (64 bit report) === kernel32: loader.c:704: Test failed: 1426: got test dll but expected fallback loader.c:704: Test failed: 1432: got test dll but expected fallback loader.c:704: Test failed: 1438: got test dll but expected fallback loader.c:704: Test failed: 1445: got test dll but expected fallback loader.c:704: Test failed: 1472: got test dll but expected fallback === w10pro64_he (64 bit report) === kernel32: loader.c:708: Test failed: 1196: wrong status c000011b/c0000130 loader.c:708: Test failed: 1201: wrong status c000011b/c0000130 loader.c:708: Test failed: 1206: wrong status c000011b/c000007b loader.c:708: Test failed: 1211: wrong status c000011b/c000007b loader.c:708: Test failed: 1216: wrong status c000011b/c000007b loader.c:708: Test failed: 1221: wrong status c000011b/c000007b loader.c:708: Test failed: 1226: wrong status c000011b/c000007b loader.c:708: Test failed: 1242: wrong status c000011b/0 === w10pro64_zh_CN (64 bit report) === kernel32: loader.c:708: Test failed: 1174: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c0000131 loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c0000130 loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1179: wrong status c000012f/c000011b loader.c:708: Test failed: 1196: wrong status c000012f/c0000130 loader.c:708: Test failed: 1201: wrong status c000012f/c0000130 loader.c:708: Test failed: 1206: wrong status c000012f/c000007b
participants (2)
-
Marvin -
Serge Gautherie