do ERR messages imply bugs?

Ben Klein shacklein at
Sun Apr 12 00:09:51 CDT 2009

2009/4/12 Vincent Povirk <madewokherd+8cd9 at>:
> On Sat, Apr 11, 2009 at 11:49 PM, chris ahrendt <celticht32 at> wrote:
>> So in the case of the multiple locks and err's the output of the test run is
>> the same for bug 7284 <> then
>> this bug or output would be invalid as well?
> The bug description claims it's about lighting effects, not err messages.

Actually, from what I've read, the bug has been traced to
peculiarities in shader code relating to 0*infinity.

> Also, the test log (whose relevance to the bug I do not understand)
> shows actual failures.

Yes, 7284 is unrelated to 17998, because it's a bug relating to
visible, graphical errors. 7284 is not exclusively about the error
output, whereas 17998 is.

The question that needs to be answered regarding 17998 is: does the
test deliberately attempt to lock the same surface multiple times? If
so, these ERRs are expected and it is either INVALID or WONTFIX. If
not, then maybe the test needs to be cleaned up.

More information about the wine-devel mailing list