The GitHub Actions job "Benchmarks PR Comment" on texera.git/main has succeeded. Run started by GitHub user Ma77Ball (triggered by Ma77Ball).
Head commit for run: aca41f3cb79b3330f4a744504b349b479a645fa2 / Matthew B. <[email protected]> ci(benchmarks): schedule-only gh-pages publish + same-runner baseline (#5671) ### What changes were proposed in this PR? - Gate the `github-action-benchmark` gh-pages publish (`auto-push` / `save-data-file`) to the `schedule` run only; PR and push-to-main runs no longer write bot commits, they still emit the job summary and uploaded artifact. The scheduled run fires **daily** at 12:00 UTC (05:00 PDT, the early-morning lull when GitHub runners are less contended and thus less noisy), so gh-pages accumulates one fresh baseline data point per day, frequent enough to average out CI noise over time. The extra daily bot commits are intentionally tolerated (the baseline data matters more than the commit count). Bumping to several times a day is a one-line cron addition later. - Add a "Benchmark main baseline in the same runner" step to `benchmarks.yml`: a PR run benches the PR head, then checks out the base `main` commit it targets, re-syncs main's Python deps (`requirements.txt` / `operator-requirements.txt` / `dev-requirements.txt`) and regenerates proto bindings so the baseline runs main's code against main's deps, then re-runs the identical trimmed grid against that commit in the same runner and adds `arrow-flight-e2e-main.csv` (plus a base-SHA sidecar) to the artifact. The step is fail-soft via a `trap` that restores the PR results and original checkout if the main re-run dies. - Update `benchmarks-pr-comment.yml` to prefer the same-runner main CSV as the comparison baseline (keyed 1:1 against the deterministic PR grid), with gh-pages still supplying the 7-day average column and a full fallback when the same-runner CSV is absent. The comment note flags when the comparison is same-runner. ### Any related issues, documentation, discussions? Closes: #5670 ### How was this PR tested? - Locally validated both workflows parse: `python3 -c "import yaml; yaml.safe_load(open('.github/workflows/benchmarks.yml')); yaml.safe_load(open('.github/workflows/benchmarks-pr-comment.yml'))"`, expect no error. - Locally syntax-checked the embedded github-script in `benchmarks-pr-comment.yml` with `node --check`, expect no error. - Behavior is CI-only and was not exercised locally. Reviewer: open a test PR carrying an amber-integration trigger label (e.g. `ci`), confirm the Benchmarks run executes the "Benchmark main baseline in the same runner" step, the run artifact contains `arrow-flight-e2e-main.csv`, and the PR comment shows the "this same runner" note with a populated main-vs-branch table. - Reviewer: confirm a PR run and a merge to main produce no new `gh-pages` commit, and that only the daily scheduled run pushes to `gh-pages`. ### Was this PR authored or co-authored using generative AI tooling? Co-authored with Claude Opus 4.8 in compliance with ASF Report URL: https://github.com/apache/texera/actions/runs/27485929566 With regards, GitHub Actions via GitBox
