Skip to content

[codex] Add orchestration tool coverage tests#30

Merged
senamakel merged 1 commit into
mainfrom
codex/coverage-tests
Jul 5, 2026
Merged

[codex] Add orchestration tool coverage tests#30
senamakel merged 1 commit into
mainfrom
codex/coverage-tests

Conversation

@senamakel

Copy link
Copy Markdown
Member

Summary

  • add focused unit coverage for graph orchestration tools through the public Tool::call path
  • cover spawn task variants, await/cancel/kill/timeout/yield, race loser cancellation, validation failures, and steering payload/terminal-task behavior
  • fix a parallel test temp-directory collision in git worktree tests by adding a monotonic suffix

Coverage

  • all-features/all-targets line coverage: 92.25%
  • src/graph/orchestration/tool.rs improved from 47.10% to 78.42%

Validation

  • rustup run stable cargo fmt --check
  • rustup run stable cargo clippy --all-features --all-targets -- -D warnings
  • rustup run stable cargo test --all-features --all-targets
  • rustup run stable cargo llvm-cov --all-features --all-targets --lcov --output-path lcov.info

@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fe1d05b5-5bad-41fb-8511-c99429a9357a

📥 Commits

Reviewing files that changed from the base of the PR and between 6bf67ac and 6fc1494.

📒 Files selected for processing (2)
  • src/graph/orchestration/test.rs
  • src/harness/workspace/git/test.rs

Comment @coderabbitai help to get the list of available commands.

@senamakel senamakel marked this pull request as ready for review July 5, 2026 11:35
@senamakel senamakel merged commit b23e213 into main Jul 5, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant