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=47424 Your paranoid android. === debian9 (32 bit report) === gdi32: font.c:1339: Test succeeded inside todo block: got 72, expected 72 (B) font.c:6147: Test succeeded inside todo block: expected 816, got 816 font.c:6150: Test succeeded inside todo block: expected 836, got 836 === debian9 (32 bit French report) === gdi32: font.c:1339: Test succeeded inside todo block: got 72, expected 72 (B) font.c:6147: Test succeeded inside todo block: expected 816, got 816 font.c:6150: Test succeeded inside todo block: expected 836, got 836 === debian9 (32 bit Japanese:Japan report) === gdi32: font.c:1339: Test succeeded inside todo block: got 72, expected 72 (B) font.c:6147: Test succeeded inside todo block: expected 816, got 816 font.c:6150: Test succeeded inside todo block: expected 836, got 836 === debian9 (32 bit Chinese:China report) === gdi32: font.c:1339: Test succeeded inside todo block: got 72, expected 72 (B) font.c:6147: Test succeeded inside todo block: expected 816, got 816 font.c:6150: Test succeeded inside todo block: expected 836, got 836 === debian9 (32 bit WoW report) === gdi32: font.c:1339: Test succeeded inside todo block: got 72, expected 72 (B) font.c:6147: Test succeeded inside todo block: expected 816, got 816 font.c:6150: Test succeeded inside todo block: expected 836, got 836 === debian9 (64 bit WoW report) === gdi32: font.c:1339: Test succeeded inside todo block: got 72, expected 72 (B) font.c:6147: Test succeeded inside todo block: expected 816, got 816 font.c:6150: Test succeeded inside todo block: expected 836, got 836