From db8ffbb07710bfd899442856703d6a82c8b64248 Mon Sep 17 00:00:00 2001
From: Lais Andrade <lsandrade@google.com>
Date: Tue, 26 Mar 2024 12:03:07 +0000
Subject: [PATCH] Remove cleanup after bench loop from setAmplitude test

Fix error on waiting for long vibration callback that might have been
already cleared by the HAL when vibration finished. Test run crash log:

FORTIFY: pthread_mutex_lock called on a destroyed mutex (0xf5a83bbc)

Keep all test cleanup logic in teardown methods.

Bug: 329899022
Change-Id: If7c13296b870e792063a9ad7b307d57fb5c333aa
Test: atest VibratorHalIntegrationBenchmark
---
 vibrator/bench/benchmark.cpp | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/vibrator/bench/benchmark.cpp b/vibrator/bench/benchmark.cpp
index dd618a5bc1..deaa6f2c55 100644
--- a/vibrator/bench/benchmark.cpp
+++ b/vibrator/bench/benchmark.cpp
@@ -493,11 +493,6 @@ BENCHMARK_WRAPPER(VibratorBench_Aidl, setAmplitude, {
             return;
         }
     }
-
-    shouldSkipWithError(state, mVibrator->off());
-    if (cb) {
-        cb->waitForComplete();
-    }
 });
 
 BENCHMARK_WRAPPER(VibratorBench_Aidl, setExternalControl, {