Scale Test CI#575
Merged
Merged
Conversation
danbar2
reviewed
May 5, 2026
danbar2
reviewed
May 5, 2026
danbar2
previously approved these changes
May 6, 2026
gflarity
reviewed
May 9, 2026
oleg-kushniriov
approved these changes
May 12, 2026
danbar2
approved these changes
May 12, 2026
d87ee34 to
80899b6
Compare
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds the first version of Grove scale-test CI history tracking.
This PR adds:
The workflow disables routine profiling/pprof collection, compiles the scale test before creating the KWOK cluster, and uploads short-retention diagnostics on failure.
Which issue(s) this PR fixes:
Fixes #550
Special notes for your reviewer:
The workflow is intentionally manual/scheduled only for v1. It does not run on PR labels.
The history branch is expected to be public and served by GitHub Pages. Routine runs store only timing history and raw scale-test JSON, not profiling artifacts.
Validation done:
Does this PR introduce a API change?
NONE
Additional documentation e.g., enhancement proposals, usage docs, etc.:
operator/hack/README.md documents scale-history.py local/branch usage and local dashboard validation.