1 Oct
2022
1 Oct
'22
8:21 p.m.
On Sat Oct 1 12:45:43 2022 +0000, **** wrote:
Marvin replied on the mailing list:
Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=124676 Your paranoid android. === w1064 (32 bit report) === kernel32: loader.c:721: Test marked flaky: 1225: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1230: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1235: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1240: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1245: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1261: wrong status c0000130/0 loader.c:721: Test marked flaky: 1265: wrong status c0000130/0 loader.c:721: Test marked flaky: 1270: wrong status c0000130/0 loader.c:721: Test marked flaky: 1274: wrong status c0000130/0 loader.c:721: Test marked flaky: 1278: wrong status c0000130/0 loader.c:721: Test marked flaky: 1317: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1326: wrong status c0000130/c000007b loader.c:721: Test marked flaky: 1331: wrong status c0000130/0 loader.c:721: Test marked flaky: 1338: wrong status c0000130/0 loader.c:721: Test marked flaky: 1345: wrong status c0000130/0 loader.c:721: Test marked flaky: 1353: wrong status c0000130/0 loader.c:721: Test marked flaky: 1360: wrong status c0000130/0 === w1064_2qxl (64 bit report) === kernel32: loader.c:721: Test marked flaky: 1220: wrong status c000011b/c0000130 loader.c:721: Test marked flaky: 1225: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1230: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1235: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1240: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1245: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1261: wrong status c000011b/0 loader.c:721: Test marked flaky: 1265: wrong status c000011b/0 loader.c:721: Test marked flaky: 1270: wrong status c000011b/0 Report validation errors: kernel32:loader has unaccounted for failure messages kernel32:loader returned success despite having failures === w10pro64 (64 bit report) === kernel32: loader.c:721: Test marked flaky: 1193: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c0000131 loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c0000130 loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1198: wrong status c000012f/c000011b loader.c:721: Test marked flaky: 1215: wrong status c000012f/c0000130 loader.c:721: Test marked flaky: 1220: wrong status c000012f/c0000130 Report validation errors: kernel32:loader has unaccounted for failure messages kernel32:loader returned success despite having failures === w10pro64_en_AE_u8 (64 bit report) === kernel32: loader.c:721: Test marked flaky: 1220: wrong status c000011b/c0000130 loader.c:721: Test marked flaky: 1225: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1230: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1235: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1240: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1245: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1261: wrong status c000011b/0 loader.c:721: Test marked flaky: 1265: wrong status c000011b/0 loader.c:721: Test marked flaky: 1270: wrong status c000011b/0 loader.c:721: Test marked flaky: 1274: wrong status c000011b/0 loader.c:721: Test marked flaky: 1278: wrong status c000011b/0 loader.c:721: Test marked flaky: 1432: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1440: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1445: wrong status c000011b/0 loader.c:721: Test marked flaky: 1451: wrong status c000011b/0 loader.c:721: Test marked flaky: 1457: wrong status c000011b/0 loader.c:721: Test marked flaky: 1464: wrong status c000011b/0 loader.c:721: Test marked flaky: 1470: wrong status c000011b/0 loader.c:721: Test marked flaky: 1479: wrong status c000011b/0 loader.c:721: Test marked flaky: 1483: wrong status c000011b/0 loader.c:721: Test marked flaky: 1487: wrong status c000011b/0 loader.c:721: Test marked flaky: 1491: wrong status c000011b/0 loader.c:721: Test marked flaky: 1495: wrong status c000011b/0 === w10pro64_ar (64 bit report) === kernel32: loader.c:721: Test marked flaky: 1220: wrong status c000011b/c0000130 loader.c:721: Test marked flaky: 1225: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1230: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1235: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1240: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1245: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1261: wrong status c000011b/0 loader.c:721: Test marked flaky: 1265: wrong status c000011b/0 loader.c:721: Test marked flaky: 1270: wrong status c000011b/0 loader.c:721: Test marked flaky: 1274: wrong status c000011b/0 loader.c:721: Test marked flaky: 1278: wrong status c000011b/0 loader.c:721: Test marked flaky: 1432: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1440: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1445: wrong status c000011b/0 loader.c:721: Test marked flaky: 1451: wrong status c000011b/0 loader.c:721: Test marked flaky: 1457: wrong status c000011b/0 loader.c:721: Test marked flaky: 1464: wrong status c000011b/0 loader.c:721: Test marked flaky: 1470: wrong status c000011b/0 loader.c:721: Test marked flaky: 1479: wrong status c000011b/0 loader.c:721: Test marked flaky: 1483: wrong status c000011b/0 loader.c:721: Test marked flaky: 1487: wrong status c000011b/0 loader.c:721: Test marked flaky: 1491: wrong status c000011b/0 loader.c:721: Test marked flaky: 1495: wrong status c000011b/0 === w10pro64_ja (64 bit report) === kernel32: loader.c:721: Test marked flaky: 1220: wrong status c000011b/c0000130 loader.c:721: Test marked flaky: 1225: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1230: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1235: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1240: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1245: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1261: wrong status c000011b/0 loader.c:721: Test marked flaky: 1265: wrong status c000011b/0 loader.c:721: Test marked flaky: 1270: wrong status c000011b/0 loader.c:721: Test marked flaky: 1274: wrong status c000011b/0 loader.c:721: Test marked flaky: 1278: wrong status c000011b/0 loader.c:721: Test marked flaky: 1432: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1440: wrong status c000011b/c000007b loader.c:721: Test marked flaky: 1445: wrong status c000011b/0 loader.c:721: Test marked flaky: 1451: wrong status c000011b/0 loader.c:721: Test marked flaky: 1457: wrong status c000011b/0 loader.c:721: Test marked flaky: 1464: wrong status c000011b/0 loader.c:721: Test marked flaky: 1470: wrong status c000011b/0 loader.c:721: Test marked flaky: 1479: wrong status c000011b/0 loader.c:721: Test marked flaky: 1483: wrong status c000011b/0 loader.c:721: Test marked flaky: 1487: wrong status c000011b/0 loader.c:721: Test marked flaky: 1491: wrong status c000011b/0 loader.c:721: Test marked flaky: 1495: wrong status c000011b/0
All flaky so it's okay. The accounting issues are because the flaky are no longer counted as failures but the TestBot was now updated.