ci: cap benchmark runtime and split its steps - #2286
Open
osbre wants to merge 1 commit into
Open
Conversation
osbre
marked this pull request as ready for review
September 7, 2026 16:02
Benchmark ResultsComparison of Open to see the benchmark resultsNo benchmark changes above ±5%. Generated by phpbench against commit 3bfaa84 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A recent benchmark run hung for ~4? hours. To isolate whether Composer or phpbench is driving the recurring ~30x performance variance, this PR splits the workflow steps so future slow runs or timeouts immediately reveal where things get stuck. It also adds a 180-minute overall job cap (giving
composer update20m andphpbench run70m) while safely accommodating historical slow-but-successful outliers.