Always run baseline benchmark first, even with --only

Summary: Otherwise, we won't end up calculating some metrics because we mistakenly think that a baseline is lacking.

Reviewed By: xuzhao9

Differential Revision: D58503025

fbshipit-source-id: 17e614794f29c07a62ab55380057905bb8eb8a60

torchbenchmark/util/triton_op.py

@@ -526,15 +526,15 @@ def run(
  if self.name in ENABLED_BENCHMARKS
  else []
  )
-  # Run the baseline first, if baseline exists
-  baseline_name = (
-  BASELINE_BENCHMARKS[self.name]
-  if self.name in BASELINE_BENCHMARKS
-  else None
-  )
-  if baseline_name and baseline_name in benchmarks:
-  benchmarks.remove(baseline_name)
-  benchmarks.insert(0, baseline_name)
+ # Run the baseline first, if baseline exists
+ baseline_name = (
+ BASELINE_BENCHMARKS[self.name]
+ if self.name in BASELINE_BENCHMARKS
+ else None
+ )
+ if baseline_name and baseline_name in benchmarks:
+ benchmarks.remove(baseline_name)
+ benchmarks.insert(0, baseline_name)
 
  # get metrics for for each registered benchmark
  def _reduce_benchmarks(acc, bm_name: str):