https://bugs.winehq.org/show_bug.cgi?id=51751
--- Comment #6 from Saulius K. saulius2@gmail.com --- (In reply to Nikolay Sivov from comment #5)
The motivation to reject on large number of failures is to avoid reports that we know are broken results.
Only that in this case developers don't know if the results are broken. Developers can only guess.
My aim is to improve the situation both for developers and test operators.
figuring out first if there is a major misconfiguration (even if from the point of view of test expectations) is preferred.
And where is the public instructions for that process?
A comment in the Bugzilla doesn't count as documentation (meaning it would be another bug, this time in WineHQ.org, I guess).