[Bug 94715] dEQP-ES31 debug tests issue quality warnings due to shader-db messages

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=94715

--- Comment #1 from Iago Toral <itoral at igalia.com> ---
I only see one such warning in the set mentioned groups of tests, this is
running on HSW with Mesa master 17353ef043beede. The particular test case
affected is:

dEQP-GLES31.functional.debug.error_filters.case_23

The problem is that the test runs twice, once without debug filters and then
again with debug filters applied and checks that messages have been filtered
properly. When we generate shader code, we emit debug messages with fragment
and vertex shader code stats (see the call to compiler->shader_debug_log() in
both vec4 and fs generators). These are logged as message type other when
shaders are compiled on the first (unfiltered) run of the test, but on the
second (filtered) run, they are not emitted because the shaders are already
compiled and do not need to be compiled again. As a result, the debug messages
with the copilation stats are not emitted and dEQP notices the change.

The reason why dEQP raises this as a warning is because with the filters used
in the second run of the test, dEQP does not disable emission of debug messages
of type OTHER, so even when it does not know why they were generated to begin
with, it warns that they are going away with the filters on and they probably
shouldn't (since it is not trying to filter them away).

In other words, dEQP does not know if the messages go away because of correct
reasons or because we have a bug with the filters. In this case, it is for
correct reasons and we don't need to fix anything.

I suggest that we close this as NOTABUG or WONTFIX at least if someone else can
verify that this is indeed the only warning we see for the groups of tests
mentioned in the bug report.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20161021/21ebb509/attachment.html>