Repository navigation
Skip C-API in workspace coverage - #8619
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe cron CI workflow excludes ChangesCoverage workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The workflow stops collecting C-API coverage from the root workspace while retaining its dedicated coverage path; this is a localized CI behavior change with no actionable merge-blocking risk remaining after normal checks. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Assisted-by: Codex:gpt-5.6-sol
0a11833 to
f2df899
Compare
|
I am sorry to miss this, Thank you @moreal and @bschoenmaeckers ! |
Assisted-by: Codex:gpt-5.6-sol
Summary
The periodic coverage job runs tests from the workspace root, which causes the rustpython-capi test binary to be built without the crate-local PyO3 configuration from crates/capi/.cargo/config.toml. The binary consequently crashes with SIGSEGV as soon as its unit tests start. This failure appeared in the run associated with #8616, but the same failure has also affected scheduled runs on main since C-API tests were enabled.
This change excludes rustpython-capi from the root workspace coverage invocation, matching the existing regular CI workflow. The C-API suite remains covered by its dedicated CI invocation from crates/capi, where all 102 tests pass with the required configuration. I also verified the remaining workspace tests, clippy, formatting, pre-commit hooks, actionlint, and the workflow security scan locally.
Summary by CodeRabbit