Francisco Jerez curroje...@riseup.net writes:
Jordan Justen jordan.l.jus...@intel.com writes:
On 2015-07-24 12:49:05, Francisco Jerez wrote:
Jordan Justen jordan.l.jus...@intel.com writes:
I don't know of any other cases where we skip a test based on the
render name. I don't think this is
Jordan Justen jordan.l.jus...@intel.com writes:
On 2015-07-24 12:49:05, Francisco Jerez wrote:
Jordan Justen jordan.l.jus...@intel.com writes:
I don't know of any other cases where we skip a test based on the
render name. I don't think this is a good practice to start.
What do you think
This test is known to cause a GPU hang on IVB due to a hardware bug.
The reason is that the hardware seems to be unable to cope with
binding table indices mapping to an invalid surface, which is
sometimes the case when a shader accesses an array of images out of
bounds.
According to the
On 2015-07-24 12:49:05, Francisco Jerez wrote:
Jordan Justen jordan.l.jus...@intel.com writes:
I don't know of any other cases where we skip a test based on the
render name. I don't think this is a good practice to start.
What do you think we should do in that case?
* Let the driver hang
I don't know of any other cases where we skip a test based on the
render name. I don't think this is a good practice to start.
-Jordan
On 2015-07-24 11:01:47, Francisco Jerez wrote:
This test is known to cause a GPU hang on IVB due to a hardware bug.
The reason is that the hardware seems to be
Jordan Justen jordan.l.jus...@intel.com writes:
I don't know of any other cases where we skip a test based on the
render name. I don't think this is a good practice to start.
What do you think we should do in that case?
-Jordan
On 2015-07-24 11:01:47, Francisco Jerez wrote:
This test is
