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=148272
Your paranoid android.
=== w1064v1507 (32 bit report) ===
mlang: mlang.c:2791: Test failed: IMLangFontLink2_MapFont: expected S_OK/128/1, got 8a1503e9/0/0 mlang.c:2796: Test failed: IMLangFontLink2_ReleaseFont: expected S_OK, got 80004005 mlang.c:2802: Test failed: MapFont() failed, hr 0x80004005. mlang.c:2805: Test failed: expected !NULL/!NULL, got 00000000/460A06A5 mlang.c:2806: Test failed: expected equal, got not equal mlang.c:2809: Test failed: code pages of font is incorrect
=== w1064v1507 (64 bit report) ===
mlang: mlang.c:2791: Test failed: IMLangFontLink2_MapFont: expected S_OK/128/1, got 8a1503e9/0/0 mlang.c:2796: Test failed: IMLangFontLink2_ReleaseFont: expected S_OK, got 80004005 mlang.c:2802: Test failed: MapFont() failed, hr 0x80004005. mlang.c:2805: Test failed: expected !NULL/!NULL, got 0000000000000000/000000001C0A0566 mlang.c:2806: Test failed: expected equal, got not equal mlang.c:2809: Test failed: code pages of font is incorrect