fix(vitest): balance profiler in walltime runner on benchmark error

Move stopBenchmark() and marker emissions into the finally block so a
throwing benchmark cannot leave the profiler started-but-never-stopped,
which would corrupt instrumentation state for subsequent benchmarks.

Author: not-matthias

packages/vitest-plugin/src/walltime/index.ts

@@ -90,18 +90,18 @@ export class WalltimeRunner extends NodeBenchmarkRunner {
       try {
         await originalRun.call(this);
       } finally {
+        const runEnd = InstrumentHooks.currentTimestamp();
+        InstrumentHooks.stopBenchmark();
         task.fn = originalFn;
-      }
-      const runEnd = InstrumentHooks.currentTimestamp();
-      InstrumentHooks.stopBenchmark();
 
-      // Emit a single marker pair covering the whole measurement run
-      InstrumentHooks.addMarker(pid, MARKER_TYPE_BENCHMARK_START, runStart);
-      InstrumentHooks.addMarker(pid, MARKER_TYPE_BENCHMARK_END, runEnd);
+        // Emit a single marker pair covering the whole measurement run
+        InstrumentHooks.addMarker(pid, MARKER_TYPE_BENCHMARK_START, runStart);
+        InstrumentHooks.addMarker(pid, MARKER_TYPE_BENCHMARK_END, runEnd);
 
-      // Look up the URI by task name
-      const uri = `${suiteUri}::${this.name}`;
-      InstrumentHooks.setExecutedBenchmark(pid, uri);
+        // Look up the URI by task name
+        const uri = `${suiteUri}::${this.name}`;
+        InstrumentHooks.setExecutedBenchmark(pid, uri);
+      }
 
       return this;
     };