refactor(tooling): adopt shared benchmark primitives - #269
Conversation
- Delegate Criterion parsing and comparisons, digest verification, archive extraction, and README section replacement to research-repo-tools. - Publish complete report, evidence, plot, and retained-summary output groups through shared transactions while preserving historical schemas and hashes. - Report invalid timings and publication failures with context, preserving existing artifacts when an operation fails. - Remove duplicate tooling and Semgrep rules, refresh subprocess policy, and update the Ruff and Semgrep pins. - Accept the benchmark-only paste maintenance advisory until January 1, 2027, while retaining checks for all other advisories. Refs #268 Refs acgetchell/research-repo-tools#64
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: acgetchell/la-stack/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour. 📝 WalkthroughWalkthroughBenchmark scripts adopt shared utilities for Criterion data, archive extraction, digest checks, document sections, and multi-file publication. Documentation and tests describe these changes and retained consumer-owned behavior. Security files record a temporary OSV exception for ChangesPerformance tooling consolidation
Temporary OSV exception
Priority: ⬇️ Low Estimated code review effort: 4 (Complex) | ~45 minutes Change: Refactor Merge Risk: ⚪ Minimal · up to The reviewed tooling and configuration changes show no supported workflow regression, so no actionable merge risk is identified in the supplied context. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #269 +/- ##
=======================================
Coverage 98.02% 98.02%
=======================================
Files 13 13
Lines 6726 6726
=======================================
Hits 6593 6593
Misses 133 133
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
- Restore Semgrep 1.178.0, whose Windows wheel includes semgrep-core.exe. - Disable Semgrep source builds so missing platform wheels fail during installation instead of leaving an unusable scanner in the environment. Refs #269
Summary
Benchmark support scripts duplicate primitives already available in the pinned research-repo-tools 0.1.7 package. Adopt those primitives while keeping la-stack's scientific eligibility, historical evidence formats, and report layout local.
pastethrough faer/gemm/pulp; it does not patch the dependency or disable other advisories.The remaining common-harness and immutable-run workflow migration stays open in #268, pending publication of acgetchell/research-repo-tools#64. The shared scanner's missing terminal diagnostics are tracked in acgetchell/research-repo-tools#65, with a live reproduction added there.
Validation
just cipassed during the Python review: 499 Python tests and 893 runnable Rust tests, plus the configured doctest, example, and benchmark-build checks.just checkandjust securitypassed after the Semgrep cleanup and security exception. OSV scanned 165 Rust and 81 Python packages with no remaining findings; Gitleaks found no secrets in reachable history or the working inventory.just checkpassed again. Locked dependency selection for Windows succeeded in a dry run; a separate Windows dry run confirmed the wheel-only policy rejects Semgrep 1.179.0, which lacks a Windows wheel.Performance
No Rust numerical kernels or benchmark definitions changed, and no timing improvement is claimed. This reduces duplicated support infrastructure while retaining the existing scientific workflow contract.