Repository navigation
test(storage): certify durability and isolation with seeded model histories - #773
Conversation
…tories Add an integrated reference state machine over the fault oracle, wire required/scheduled certification evidence, and close the final M6 matrix cells. Closes #756 Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 23 minutes Limit details: You’ve used all 1 included review currently available under your plan. You completed 63 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour. 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 ignored due to path filters (3)
📒 Files selected for processing (16)
Comment |
This comment has been minimized.
This comment has been minimized.
…ions Use the approved upload-artifact v7 pin with fail-closed retention, and compare commit generations only against fresh-open recovery (pinned facades stay put). Co-authored-by: Cursor <cursoragent@cursor.com>
Merging this PR will degrade performance by 28.47%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ❌ | lex[simple_match] |
26 µs | 36.3 µs | -28.47% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing test/756-durability-isolation-cert (4b415f6) with main (ba78134)
Summary
project_certification) over the fault oracle covering acknowledgement, restart, pinned readers, write modes, checkpoints, deltas, compaction, GC, cancellation, process-death boundaries, and media faultsgraphforge-durability-certification/1, seed7560) with fail-closed evidence artifacts; flipwrite_skewandseeded_model_certificationmatrix cells to coveredTest plan
cargo test -p graphforge-storage --features test-failpoints project_certification --libcargo test -p graphforge-api --lib durability_certification_testscargo test -p graphforge-api --lib optimistic_write_skew_witness_matches_isolation_tablecargo clippy -p graphforge-storage --features test-failpoints -- -D warningspython3 scripts/ci/durability-isolation-gate.py validatepython3 scripts/ci/durability-certification-gate.py validatepython3 scripts/ci/test-durability-isolation-gate.pypython3 scripts/ci/test-durability-certification-gate.pyCloses #756
Made with Cursor
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.