All uses of the UUR_KNOWN_FAILURE_ON macro in the CTS should ideally be accompanied by a link to an issue, or, if the fail is due to something out of our control, an explanation as to why. This issue represents a quick collating of all the OpenCL KNOWN_FAILUREs, subtasks should be spun out to coordinate working on individual cases.
All uses of the
UUR_KNOWN_FAILURE_ONmacro in the CTS should ideally be accompanied by a link to an issue, or, if the fail is due to something out of our control, an explanation as to why. This issue represents a quick collating of all the OpenCL KNOWN_FAILUREs, subtasks should be spun out to coordinate working on individual cases.