https://bugs.winehq.org/show_bug.cgi?id=51751
--- Comment #8 from Saulius K. saulius2@gmail.com --- (In reply to Nikolay Sivov from comment #7)
Instructions for what?
I am referring to this process:
figuring out first if there is a major misconfiguration
To detect a major misconfiguration means to check a specific list of configuration items/settings on a system (like the DPI setting you mentioned).
I get this following: if developer says "misconfiguration", to be constructive the one should have quite specific definition of it at ones hand.
Which is what I miss (a configuration checkup list/tool). Does this mean the project haven't documented any such such measure?
Winetest gives you a warning, explaining why results were not submitted.
I may repeat myself, but for non-developer the explanation is too lose/broad to start looking at results.
If you want to make tests run cleaner on that configuration, take a look at the log to see what fails the most, and start from there.
OK, particularly which things do you mean by "what" here, a:
* per-DLL failures, * per-function-group failures, * per-specific-function failures, * per-speficif-line failures.
As former contributor, I ask for being specific, particular, not for the generalizations. A documentation URL would do too. Thanks:)