#Centipede Improve accuracy of reported fuzz time and execs/sec stats

Moved the fuzz time resetting to after the first telemetry dump. Telemetry can take non-trivial time in some cases, skewing some of the reported stats.

PiperOrigin-RevId: 617235131

centipede/centipede.cc

diff --git a/centipede/centipede.cc b/centipede/centipede.cc
index 9c1808a..e295a3d 100644
--- a/centipede/centipede.cc
+++ b/centipede/centipede.cc
@@ -720,11 +720,6 @@
 
   UpdateAndMaybeLogStats("init-done", 0);
 
-  // Clear fuzz_start_time_ and num_runs_, so that the pre-init work doesn't
-  // affect them.
-  fuzz_start_time_ = absl::Now();
-  num_runs_ = 0;
-
   // If we're going to fuzz, dump the initial telemetry files. For a brand-new
   // run, these will be functionally empty, e.g. the coverage report will list
   // all target functions as not covered (NONE). For a bootstrapped run (the
@@ -733,6 +728,11 @@
   // configured (the same number of shards, for example).
   if (env_.num_runs != 0) MaybeGenerateTelemetry("initial", "Before fuzzing");
 
+  // Reset fuzz_start_time_ and num_runs_, so that the pre-init work doesn't
+  // affect them.
+  fuzz_start_time_ = absl::Now();
+  num_runs_ = 0;
+
   // num_runs / batch_size, rounded up.
   size_t number_of_batches = env_.num_runs / env_.batch_size;
   if (env_.num_runs % env_.batch_size != 0) ++number_of_batches;