Summary: | [SNB+ Bisected]Piglit spec_ARB_texture_storage_multisample_tex-param fails | ||
---|---|---|---|
Product: | piglit | Reporter: | lu hua <huax.lu> |
Component: | tests | Assignee: | Piglit Mailing List <piglit> |
Status: | VERIFIED FIXED | QA Contact: | Piglit Mailing List <piglit> |
Severity: | normal | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
lu hua
2015-01-09 06:56:11 UTC
This bug is fixed by the series I pushed to Mesa yesterday: http://cgit.freedesktop.org/mesa/mesa/commit/?id=f4dce7a6a69de30ab7aad7612f93302c69421fea Verified.Fixed on mesa master branch. output: libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so libGL: Error in /etc/drirc line 1, column 0: no element found. libGL: Error in /root/.drirc line 1, column 0: no element found. libGL: Error in /etc/drirc line 1, column 0: no element found. libGL: Error in /root/.drirc line 1, column 0: no element found. PIGLIT: {"subtest": {"GL_TEXTURE_IMMUTABLE_FORMAT" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_MAG_FILTER" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_MIN_FILTER" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_WRAP_S" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_WRAP_T" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_WRAP_R" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_COMPARE_MODE" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_COMPARE_FUNC" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_MIN_LOD" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_MAX_LOD" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_BASE_LEVEL zero" : "pass"}} PIGLIT: {"subtest": {"GL_TEXTURE_BASE_LEVEL nonzero" : "pass"}} PIGLIT: {"result": "pass" } In the future, if you know a test change will cause the test to fail, note that in the commit message. By doing this, QA won't spend time (yours and theirs) submitting a bug report. Commit 8797b318 is an example. |
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.