Change CI Perf to run on schedule, no runs on PRs#1646
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1646 +/- ##
============================================
+ Coverage 99.00% 99.14% +0.13%
Complexity 962 962
============================================
Files 197 197
Lines 2214 2215 +1
============================================
+ Hits 2192 2196 +4
+ Misses 22 19 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Updates the CI performance benchmark workflow to stop running on pull requests and instead run on a daily schedule plus pushes to main, aiming to gather benchmark history while avoiding PR friction.
Changes:
- Switch
ci-perftriggers toschedule(daily) andpushtomain, removingpull_requesttriggers. - Simplify phpbench execution to always compare against
latestusing--tolerate-failure. - Make the benchmark job non-blocking via
continue-on-error: true.
Comments suppressed due to low confidence (1)
.github/workflows/ci-perf.yml:21
workflow_dispatchexposes arebaselineoption, but the workflow currently only commits benchmark/baseline updates onpushevents. That means a manualrebaselinerun won’t actually update thebenchmarksbranch. Consider allowing the “Commit Results” logic to run forworkflow_dispatch(at least whenbaseline == rebaseline) so the input has the intended effect.
workflow_dispatch:
inputs:
baseline:
description: 'Baseline mode. latest: compare against latest benchmarks; rebaseline: store new baseline.'
type: choice
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
4af17bc to
b3ec46e
Compare
4a60146 to
ff9d4e5
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
See Respect#1635 The goal is to collect data for a while. Until we have enough benchmarks, the PR check is not very useful, so it was disabled. We added `--tolerate-failure` to all runs, so this check will never fail because of a missed performance assertion, but it will report it and archive it.
ff9d4e5 to
cba9efd
Compare
See #1635
The goal is to collect data for a while. Until we have enough benchmarks, the PR check is not very useful, so it was disabled.
We added
--tolerate-failureto all runs, so this check will never fail because of a missed performance assertion, but it will report it and archive it.