ci: Skip benches during release workflows - #4686
Merged
Merged
Conversation
📊 Tachometer Benchmark ResultsSummaryduration
usedJSHeapSize
Resultscreate10kduration
usedJSHeapSize
filter-listduration
usedJSHeapSize
hydrate1kduration
usedJSHeapSize
many-updatesduration
usedJSHeapSize
replace1kduration
usedJSHeapSize
run-warmup-0
run-warmup-1
run-warmup-2
run-warmup-3
run-warmup-4
run-final
text-updateduration
usedJSHeapSize
tododuration
usedJSHeapSize
update10th1kduration
usedJSHeapSize
|
|
Size Change: 0 B Total Size: 78.4 kB ℹ️ View Unchanged
|
rschristian
force-pushed
the
ci/skip-benches-on-release
branch
3 times, most recently
from
February 18, 2025 06:37
3ddb9a4 to
2ede918
Compare
rschristian
marked this pull request as ready for review
February 18, 2025 06:38
JoviDeCroock
approved these changes
Feb 18, 2025
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
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.
Our filter pattern is a bit broad, it picks up changes to
devtools/src/devtools.jswhich gets altered on every release: #4684 (comment)Should be fine to exclude it specifically, none of our benchmarks depend on it anyhow.
Edit: The PR Reporter action is expected to run on this PR as the running version is that on
main, not this PR. The benches, however, should be skipped as a result. Workflow showing this.