ci(benchmark): wait for base branch benchmark run to complete

[Dunqing]

This PR introduces a new job to the benchmark workflow to ensure the base branch's benchmark run has completed before starting the current benchmark.

This is important for benchmarking because the current branch's benchmark would compare with the base branch's benchmark result. When we create some PRs at the same time, the current branch's benchmark may be done before the base branch's benchmark; no benchmark can be compared, and the benchmark result would show N/A

The benchmark graph is like:

See https://github.com/oxc-project/oxc/actions/runs/14749573518?pr=10710

NOTE: The code was generated by the Gemini 2.5 Pro AI. I just told him what I thought and verified the code to see if it works.

[Dunqing]

• ci(benchmark): test waiting base branch benchmark ci #10710
• ci(benchmark): wait for base branch benchmark run to complete #10708 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #10708 will not alter performance

_{Comparing 04-30-ci_benchmark_wait_for_base_branch_benchmark_run_to_succeed (0f7d70d) with main (9e557cf)}

Summary

✅ 36 untouched benchmarks

[Copilot]

Pull Request Overview

This PR ensures that the benchmark job waits until the base branch's benchmark run has been completed before proceeding, enabling an accurate comparison between the two runs.

• Introduces a new job ("check-base-benchmark") that monitors the latest workflow run on the base branch.
• Updates subsequent jobs ("benchmark" and "benchmark-linter") to depend on the new job, ensuring proper sequencing.