[Bug 51751] Too many Winetest failures on w10 Pro 20H2 (on physical machine)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51751

--- Comment #4 from Saulius K. <saulius2 at gmail.com> ---
(In reply to Nikolay Sivov from comment #3)
> If you want to understand and fix some of these failures, you'll have to
> look module by module. 

That's what I want to do (or be done by someone else) in the end.

Now I want to report that Winetest reporting logic contains some serious flaw.

Results generated on the clean install of the supported OS on a branded machine
_should not_ be rejected in a such (non-verbose) manner, IMO.

Results should be either:

(1) rejected with saying where exactly the testing operator should look
(telling difference at the large scale metrics compared to the accepted
results). Or
(2) accepted by the server in usual manner so the testing operator can see it
on https://test.winehq.org/data by oneself.

Which one is more appropriate for the current workflow?
Or is there any argument to reject both proposed ways?

> Is it possible you're running with dpi above 96? If
> that's the case, you could set it to traditional default, and see if that
> improves numbers.

Thanks for the hint. I will test that ASAP. 

In case it helps, it still will not in general (for other, uninformed test
operators / testing contributors).

A change in reporting logic is still needed, IMO.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.