ci: report-only smoke-test-coverage check (inbox#20/#21) - #398
Conversation
inbox#20 entry-to-main criterion: each package should carry >=1 Standalone buildspec test that meaningfully exercises it (distinct from upstream's own tests). This reports coverage; it's the third report-only promotion signal after #279 (version-age) and #280 (closure), alongside the dwell check. smoke_test_report.py detects a Standalone test per package (the `standaloneTest "..."` helper or an explicit `class = 'Standalone`) by scanning tracked build.ncl -- no dump, no network, no secrets. Runs on pull_request into main (changed packages) and workflow_dispatch (full-catalog coverage dashboard). Hardened like version-age.yml (pinned SHA, contents:read, report-only) and MUST NOT be a required check. Current catalog coverage: 119/390 (30%). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Why
An inbox#20 entry-to-
maincriterion: each package should carry ≥1 Standalone buildspec test that meaningfully exercises it (distinct from the upstream project's ownmake test). This is the third report-only promotion signal — after #279 (upstream version-age) and #280 (stable closure), alongside the new dwell check (#397) — and the biggest Phase-1 gate that was entirely unbuilt.What
smoke_test_report.pydetects a Standalone test per package — either thestandaloneTest "..."helper or an explicitclass = 'Standalone— by scanning trackedbuild.ncl. Pure text: nominimal dump, no network, no secrets.smoke-test-coverage.ymlruns it onpull_request → main(changed packages — the entry gate) andworkflow_dispatch(full-catalog coverage dashboard). Hardened exactly likeversion-age.yml(pinned action SHA,contents: read, report-only) and must not be a required check.Current coverage (full catalog)
So ~271 packages have no Standalone test today — the report names them with a copy-paste snippet to add one.
Notes
Building block for gominimal/inbox#20 (smoke-test criterion) · gominimal/inbox#21.
🤖 Generated with Claude Code