Skip to content

A
angle
Commit 6c4af0c3 by Cody Northrop Committed by Commit Bot
Options

Tests: Add a common framebuffer config for perf tests

As we add traces tests, some were recorded expecting depth as an attachment to framebuffer 0. This causes errors when they unconditionally query info about depth attachments. Since perf tests have never requested a config before (they are all DONT_CARE for each componenent), go ahead and set one shared by all. Test: angle_perftests Bug: b/157158456 Change-Id: I83ef1a58f246bfbc98c3bc7e024aca01560107f7 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2210966 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by: 's avatarCourtney Goeltzenleuchter <courtneygo@google.com> Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
parent ce285f43
Showing with 8 additions and 0 deletions
src/tests/perf_tests/ANGLEPerfTest.cpp
......@@ -506,6 +506,14 @@ void ANGLERenderTest::SetUp()
EGLPlatformParameters withMethods = mTestParams.eglParameters;
withMethods.platformMethods = &mPlatformMethods;
// Request a common framebuffer config
mConfigParams.redBits = 8;
mConfigParams.greenBits = 8;
mConfigParams.blueBits = 8;
mConfigParams.alphaBits = 8;
mConfigParams.depthBits = 24;
mConfigParams.stencilBits = 8;
if (!mGLWindow->initializeGL(mOSWindow, mEntryPointsLib.get(), mTestParams.driver, withMethods,
mConfigParams))
{
......
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