Disable HugeSetDataShouldNotCrash test.

This test flakes out on some Chromium bot configurations. It could be that we need to redesign it to use mocks or something similar to test reliably. Change-Id: Ib323940d52db052e18d2352e45e029bbb1b64af0 Reviewed-on: https://chromium-review.googlesource.com/242023Tested-by: Jamie Madill <jmadill@chromium.org> Reviewed-by: Geoff Lang <geofflang@chromium.org>

Disable HugeSetDataShouldNotCrash test.
e50bf15f · Jamie Madill · fab29759 · e50bf15f
Commit e50bf15f authored Jan 20, 2015 by Jamie Madill
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 1 deletion

BufferDataTest.cpp tests/angle_tests/BufferDataTest.cpp +3 -1

No files found.
--- a/tests/angle_tests/BufferDataTest.cpp
+++ b/tests/angle_tests/BufferDataTest.cpp
@@ -132,7 +132,9 @@ TYPED_TEST(BufferDataTest, NULLResolvedData)
    drawQuad(mProgram, "position", 0.5f);
 }

-TYPED_TEST(BufferDataTest, HugeSetDataShouldNotCrash)
+// Tests that a huge allocation returns GL_OUT_OF_MEMORY
+// TODO(jmadill): Figure out how to test this reliably on the Chromium bots
+TYPED_TEST(BufferDataTest, DISABLED_HugeSetDataShouldNotCrash)
 {
    glBindBuffer(GL_ARRAY_BUFFER, mBuffer);
    EXPECT_GL_NO_ERROR();