Merged
Conversation
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.
Problem
Local post-release UAT for v1.3.4 was failing in
quality_perf_bench_checkbecause the UAT path was reusing the strict baseline-regression perf gate after a long local validation run, which made the outcome sensitive to local host variance.Changes
bench-uat-checktarget for local UAT that keeps absolute perf/context budget validation without reusing the stricter pre-release regression gateValidation
./gait doctor --jsonmake prepush-fullmake bench-uat-checkGAIT_UAT_RELEASE_VERSION=v1.3.4 bash scripts/test_uat_local.sh