It seems like there are 3 Windows 10 1507 machines that had this issue: * Based on the bug one was cw-gtx560-1507 (bare metal, NVIDIA GTX560 GPU). I don't see any trace of this in my archives (which go back to 2022-04-26). In any case this machine was decommissioned on 2022-05-31 so it cannot happen there anymore. * In my archives I see this happening on cw-rx460-1507 (identical bare metal, AMD RX460 GPU), until a few days before it was decommissioned (the case and PSU were reused to build gpu1). Again that explains why it does not happen anymore. * And this also happened on newtb-w1064v1507-32. That snapshot was created on 2022-04-24 and the failure happened on the following dates: 2022-05-18, 2022-05-24 and 2022-06-16. So there is nothing to explain why it has not happened since. Maybe the failure is caused by a previous test that changed, or there's some subtle timing aspect that changed. Given that there could already almost be a month between two occurrences it's also hard to pinpoint a date when the issue 'stopped'.
While Win7 is still "supported" for tests it has no priority to be added to the CI; I've watched Alexandre's gitlab roadmap presentation.
Right. And yet nobody is responsible for deciding which configurations to no longer test on.
With broken() being superior to flaky as it applies only to Windows results
The proposal to have a flaky_windows() macro was rejected. But one can still achieve the same result with flaky_if(strcmp(winetest_platform, "windows") == 0) (but I give no guarantee that it would be accepted).
That area of the code needs more work, most likely a rewrite
Would you be willing to take on the cleanup of that test code?