[Bug 93029] Hangcheck timer too agressive to pass dEQP for SNBGT1

[bugzilla-daemon at freedesktop.org]

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

--- Comment #16 from Mark Janes <mark.a.janes at intel.com> ---
Mika: this bug is not a regression, and does not block a release.  There may be
a point (soon) at which Google will require stricter dEQP conformance, but
based on the list here, the long_running_shaders are not required.

https://android.googlesource.com/platform/external/deqp/+/4423ddaeef6c6a252152f774b76950f62c412f94/android/cts

However, the hang detection's intermittent firing on *other* non-hanging dEQP
tests creates instability in the test suite.  The patch you attached to this
bug improves stability, and I haven't seen any spurious dEQP failures using it
on SNB (long-running-tests are disabled in CI).

(In reply to Mika Kuoppala from comment #15)
> (In reply to Eero Tamminen from comment #12)
> > (In reply to Mark Janes from comment #10)
> > > With Mika's patch, spurious hangchecks can still be generated by invoking
> > > the the tests listed in the comments (long_running_shaders).  These tests
> > > are blacklisted by Chrome's test suite.
> > > 
> > > The good news is that all of the *intermittent* gpu hangs that were
> > > generated by the rest of the suite have been fixed by this patch.
> > 
> > Are the still hanging tests too heavy for a slow GPU like SNB GT1?
> > 
> > What if the hang period would just be increased while running them?
> 
> I would like to understand the tests a little better and try to improve the
> heuristics, before adding a tunable.
> 
> Is this still blocking a release?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151214/1c912499/attachment.html>