Perf Tests: Run at least 1 step.

We could end up in some very slow scenes (e.g. when debugging). This could produce a step count of zero which doesn't make sense. Noticed while capturing the T-Rex replay. Bug: angleproject:5134 Change-Id: Ibf2439961dfb3c01649dcab37acead7b6e2ab345 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2449160 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by: Cody Northrop <cnorthrop@google.com> Reviewed-by: Courtney Goeltzenleuchter <courtneygo@google.com>

Perf Tests: Run at least 1 step.
974c2371 · Jamie Madill · Commit Bot · bc4ec4c1 · 974c2371
Commit 974c2371 authored Oct 04, 2020 by Jamie Madill Committed by Commit Bot Oct 06, 2020
Show whitespace changes
Inline Side-by-side

Showing with 1 addition and 0 deletions

ANGLEPerfTest.cpp src/tests/perf_tests/ANGLEPerfTest.cpp +1 -0

No files found.
--- a/src/tests/perf_tests/ANGLEPerfTest.cpp
+++ b/src/tests/perf_tests/ANGLEPerfTest.cpp
@@ -358,6 +358,7 @@ void ANGLEPerfTest::calibrateStepsToRun()
    // Scale steps down according to the time that exeeded one second.
    double scale = gTestTimeSeconds / elapsedTime;
    mStepsToRun  = static_cast<unsigned int>(static_cast<double>(mNumStepsPerformed) * scale);
+    mStepsToRun  = std::max(1, mStepsToRun);
    if (gVerboseLogging)
    {