<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [g965] glsl-1_20.execution.clipping.fixed-clip-enables fails when run concurrently"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=89398">89398</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[g965] glsl-1_20.execution.clipping.fixed-clip-enables fails when run concurrently
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Mesa
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Drivers/DRI/i965
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>idr@freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>mark.a.janes@intel.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>intel-3d-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>There appears to be a clipping regression for g965.

in addition to the test in the summary,
spec.glsl-1_10.execution.clipping.clip-plane-transformation pos_clipvert fails
in the same way.

Both tests pass when run independently.  Looping several thousand times on the
single test does not reproduce the failure.

They fail when piglit is running the whole suite, either in parallel or
sequentially.

Also, you can reproduce the failure by looping on the test and running some
other workload like shaderdb.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>