Don't check color outcome for tests that expect undefined behaviour
authorAlejandro Piñeiro <apinheiro@igalia.com>
Thu, 26 Sep 2019 09:55:49 +0000 (11:55 +0200)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 14 Nov 2019 14:48:06 +0000 (09:48 -0500)
commitce9e355c661f66828c7c173c7bda0859a3902689
tree875cc51370683274099b4eb4d51d2734dd363c1b
parentf2c8914da99f845d3abd907414ae4fd4e29864df
Don't check color outcome for tests that expect undefined behaviour

draw_indirect.misc-reservedMustBeZero-elements and its arrays
equivalent for both OpenGL and OpenGL ES tests the following paragraph
from the spec:

  "Results are undefined if reservedMustBeZero is non-zero, but must
   not lead to GL interruption or termination."

So it should check if there is no errors or crashes. But right now
those tests are also expecting a given color, that doesn't make sense
if the expected behaviour by spec is undefined.

This seems a C&P error from other tests.

Components: OpenGL, OpenGL ES

VK-GL-CTS issue: 2023

Affects:
KHR-GL41.draw_indirect.misc-reservedMustBeZero-arrays
KHR-GL41.draw_indirect.misc-reservedMustBeZero-elements
KHR-GLES31.core.draw_indirect.misc-reservedMustBeZero-arrays
KHR-GLES31.core.draw_indirect.misc-reservedMustBeZero-elements

Change-Id: I3e9a5d04893eec9359b55ea6c5130e940c943cf2
external/openglcts/modules/gles31/es31cDrawIndirectTests.cpp