fix: disable warmup to prevent additional markers

When running the warmup, we already call `start/stop_benchmark` which creates two memory profiles per benchmark, which breaks our assumptions in the backend.

Author: not-matthias

google_benchmark/src/benchmark_api_internal.cc

@@ -97,14 +97,6 @@ State BenchmarkInstance::RunSimulation(
     internal::ThreadManager* manager,
     internal::PerfCountersMeasurement* perf_counters_measurement,
     ProfilerManager* profiler_manager) const {
-  // Do one repetition to avoid flakiness due to inconcistencies in CPU cache
-  // from execution order
-
-  internal::ThreadTimer warmup_timer = internal::ThreadTimer::Create();
-  State warmup_state(name_.function_name, 1, args_, 0, 1, &warmup_timer,
-                     manager, perf_counters_measurement, profiler_manager,
-                     NULL);
-  benchmark_.Run(warmup_state);
 
   State st(name().str(), 1, args_, 0, 1, timer, manager,
            perf_counters_measurement, profiler_manager, codspeed);