Skip to content

v0.22.5 — scoped held-out perf ratchets

Choose a tag to compare

View all tags
@odvcencio odvcencio released this 09 Jul 11:05
v0.22.5
483c554
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Scoped held-out perf-ratchet release. This follows the fleet coverage cut with the exclusion machinery and ledger language needed to keep Wave 3 honest.

Added

  • perf-scan file exclusion support for reproducible scoped reruns, including GTS_PERF_SCAN_EXCLUDE_PATHS, persisted scoreboard config, and status reporting for measurement-basis exclusions.
  • perf_scan_status coverage accounting for scoped held-out budget rows, separating budgeted-with-caveat languages from ordinary green rows and hard held-outs.
  • Groovy Wave-3 scoped held-out budget row excluding groovy/subprojects/performance/src/files/pleac11_15.groovy, with observed full-parse and no-edit ratios recorded from the Docker perf sweep.

Changed

  • The perf-ratchet policy now treats expansion of measurement_basis.exclude_paths as budget loosening that requires the same RCA evidence as loosening a ratio threshold.
  • F# and D Wave-3 ledger entries now carry the exact C-reference timeout/RSS witnesses found by scoped reruns instead of presenting them as ordinary unmeasured gaps.

Caveat

D and F# remain explicit held-outs because their current large-file witnesses fail in the C-reference side or hit the harness RSS watchdog before a stable Go-vs-C ratio can be ratcheted.

Assets 2
Loading