Repository navigation
evidence(OMN-15337): rebind infra PR 2665 current head - #6182
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 10 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
Comment |
…starvation false-fails (#6230) * fix(OMN-15765): raise check-bot-authored-authz-guard timeout to stop starvation false-fails check-bot-authored-authz-guard was firing red on 12/17 open D-cluster PRs, including 5 human-authored (occ#6172/#6175/#6176/#6182/#6188). Pulled the failing job logs for occ#6176 and occ#6182: both die inside actions/checkout@v7 (fetch-depth: 0) / the setup-uv composite with conclusion=cancelled at the job's timeout-minutes: 5 wall, never reaching the guard's own decision-logic step. CI Summary's fail-closed != success comparison then scores that cancellation as an authz REJECT. This is CI-scheduling starvation, not a matcher defect -- the identity/path matcher (evaluate() in check_bot_authored_authz_guard.py) is already unit-tested correct in both directions and is unchanged here. Corroborated by OMN-15722/PR #6173, which raised nine sibling ci-summary jobs on the same preamble-latency evidence (checkout observed up to 22m38s in one run). Raises only check-bot-authored-authz-guard's timeout-minutes 5 -> 45 (matching OMN-15722's floor) and adds a regression test (test_bot_authored_authz_guard_timeout_omn15765.py) pinning the floor, proven red-before (fails at 5) / green-after (passes at 45). OMN-15765 * evidence(OMN-15765): DoD receipts for authz-guard timeout fix Adds PASS receipts for both dod_evidence items in contracts/OMN-15765.yaml (dod-authz-guard-timeout-raised, dod-authz-guard-matcher-unchanged-both-dirs), required for occ-preflight eligibility on this PR. OMN-15765 * fix(OMN-15765): reword ci.yml comment to clear the runner-label naming gate The prior comment's wording ("contended self-hosted omnibase-ci fleet") literally embedded the two centralized runner-selector labels outside the fromJSON(vars.OMNI_TRUSTED_CI_RUNS_ON_JSON || ...) form, which trips omni-standards-compliance.yml's hard-coded-runner-label scan (CI Naming Convention). Reworded to describe the same fact without repeating the literal label strings. No behavior change. OMN-15765
jonahgabriel
added
the
ci:ready
1 participant
Summary
Validation