Bug 108571 - flaky results from glescts geometry_shader.layered_rendering_boundary_condition.layered_rendering_boundary_condition_no_default_layer
Summary: flaky results from glescts geometry_shader.layered_rendering_boundary_conditi...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Jason Ekstrand
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-26 18:21 UTC by Mark Janes
Modified: 2019-09-25 19:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Mark Janes 2018-10-26 18:21:39 UTC
On a very intermittent basis, this test (in GLESEXT and GLES32 conformance tests) fails on skl, kbl, and cfl with:

Rendered data for [x=3 y=0 attachment=0 layer=0] [0, 0, 0, 0] are different from reference data [255, 255, 255, 255] !
Comment 1 Jason Ekstrand 2018-10-27 21:44:48 UTC
I've sent patches which I think will fix it:

https://bugs.freedesktop.org/show_bug.cgi?id=108571
Comment 2 Clayton Craft 2019-08-02 16:33:01 UTC
Seems like this test is flaky again on gen9 hardware:

https://mesa-ci.01.org/mesa_master_daily/test/1c93aaf9dc6654ce5d2df42e38d6d90c/history

(sort by 'hardware', see 2 failures in last few days on gen9)

Test output is a little different than last time:

    Rendered data for [x=0 y=0 attachment=0 layer=0] [0, 0, 0, 0] are different from reference data [255, 255, 255, 255] !

https://mesa-ci.01.org/mesa_master_daily/builds/5145/results/753064000
Comment 3 Denis 2019-08-05 12:19:08 UTC
Hello. Just a side note - tested this test in a loop (about 100-200 times) on latest mesa from git on these HW => CFL, KBL, SKL.

Didn't see any failures.
Comment 4 GitLab Migration User 2019-09-25 19:14:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1767.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.