Am Freitag, 26. Oktober 2007 01:54:59 schrieb Reece Dunn:
> This is true. The tests should only check for valid Windows results.
>> The problem is how to filter out the noise of the VMware bugs from
> actual failures in Windows for the Wine tests. This is so that we know
> which tests need fixing (so that the Wine behaviour can be corrected),
> and those that don't.
>> Thinking about this, my idea of updating the tests for the broken
> VMware implementation was wrong. However, I don't have a better
> solution.
I guess the only way is to skip ddraw/d3d tests entirely on vmware, or disable
3D acceleration in vmware, then the tests should skip themselves or run with
the reference rasterizer.
> > Appart of that, with these specific tests I have seen one failure on a
> > real windows box too, perhaps I should loosen the test precision on some
> > of those tests(This was in the area of 0.000x, not a difference of 129
> > and 133).
>> Having a +/- 0.000x tolerance is sensible.
Yeah, I have that, perhaps it is not enough. I didn't investigate that yet,
though
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20071026/5b439c3c/attachment.pgp