Commit fa416b18 by Jamie Madill Committed by Commit Bot

Disable ValidationESTest.DrawElementsWithMaxIndexGivesError.

Temporarily until we have a proper fix. BUG=chromium:708835 Change-Id: I9c1d63d8d1f831f2a4a168149b7ff805bc851def Reviewed-on: https://chromium-review.googlesource.com/469967Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org>
parent 6f1c3de9
...@@ -57,7 +57,8 @@ class MockValidationContext : public ValidationContext ...@@ -57,7 +57,8 @@ class MockValidationContext : public ValidationContext
// Test that ANGLE generates an INVALID_OPERATION when validating index data that uses a value // Test that ANGLE generates an INVALID_OPERATION when validating index data that uses a value
// larger than MAX_ELEMENT_INDEX. Not specified in the GLES 3 spec, it's undefined behaviour, // larger than MAX_ELEMENT_INDEX. Not specified in the GLES 3 spec, it's undefined behaviour,
// but we want a test to ensure we maintain this behaviour. // but we want a test to ensure we maintain this behaviour.
TEST(ValidationESTest, DrawElementsWithMaxIndexGivesError) // TODO(jmadill): Re-enable when framebuffer sync state doesn't happen in validation.
TEST(ValidationESTest, DISABLED_DrawElementsWithMaxIndexGivesError)
{ {
auto framebufferImpl = MakeFramebufferMock(); auto framebufferImpl = MakeFramebufferMock();
auto programImpl = MakeProgramMock(); auto programImpl = MakeProgramMock();
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment