Summary: | [Regression, bisected] arb_direct_state_access.texunits piglit test broken | ||
---|---|---|---|
Product: | Mesa | Reporter: | Mark Janes <mark.a.janes> |
Component: | Drivers/DRI/i965 | Assignee: | Brian Paul <brian.e.paul> |
Status: | CLOSED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | blocker | ||
Priority: | medium | CC: | lemody, mark.a.janes, vlee |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Mark Janes
2015-10-01 17:23:03 UTC
this one has a bit of strange history where there was a debate about correct error ... see following Piglit commit: 9b445f7a68146f50222a4162b5f7ec68c043e851 I've sent a fix to texunits test so that it expects same error as bind-texture test. *** Bug 92264 has been marked as a duplicate of this bug. *** commit d9e3621a2eb6deb12a326ed1376a7ae45a1c9d52 Author: Brian Paul <brianp@vmware.com> Date: Wed Sep 30 15:27:56 2015 -0600 arb_direct_state_access-texunits: fix incorrect error test Check for GL_INVALID_VALUE, not GL_INVALID_OPERATION. The extension spec isn't clear on this, but GL_INVALID_VALUE is typically generated for out-of-range int/uint values. That's what NVIDIA does. Plus, that's what the other bind-texture-unit piglit test checks for at line 91. Let's at least be consistent. Reviewed-by: Tapani Pälli <tapani.palli@intel.com> |
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.