These failing test are dependent on the load of the VM at the time. Should we just adjust the timeout to something like 5/10 seconds? The V2 failed initially but with the increased timeout it passed when manually run. https://testbot.winehq.org/JobDetails.pl?Key=57310 Regards Alistair. ________________________________ From: Marvin <testbot(a)winehq.org> Sent: Thursday, 3 October 2019 10:52 AM To: leslie_alistair(a)hotmail.com <leslie_alistair(a)hotmail.com> Cc: wine-devel(a)winehq.org <wine-devel(a)winehq.org> Subject: Re: [PATCH v3] dmime/tests: Add a notification_type test 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftestbot.winehq.org%2FJobDetails.pl%3FKey%3D57311&data=02%7C01%7C%7C894d515dde6c404ff6e508d7479eb34a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637056619248192726&sdata=FLKJGkBoQEOJHj6p%2F%2FIWxEI6aErz9rZrNgkgN5KkN5I%3D&reserved=0 Your paranoid android. === w1064v1507 (32 bit report) === dmime: performance.c:432: Test failed: Failed: 258 performance.c:469: Test failed: Wrong end segment performance.c:470: Test failed: Didn't recieve DMUS_NOTIFICATION_SEGEND message