Remove macos skips by arihant2math · Pull Request #5794 · RustPython/RustPython
Walkthrough
The CI workflow configuration was updated to remove the MACOS_SKIPS environment variable and its usage. Now, macOS test runs do not skip any additional tests beyond the platform-independent ones, simplifying the test exclusion logic for macOS in the workflow.
Changes
| File(s) | Change Summary |
|---|---|
| .github/workflows/ci.yaml | Removed MACOS_SKIPS environment variable and its usage in test steps |
Poem
A hop through the CI, so spry and neat,
No more skips for Mac beneath our feet.
The tests now run with fewer rules,
Streamlined steps, no extra tools.
With every leap, our code feels light—
Hopping forward, tests in sight!
🐇✨
📜 Recent review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/ci.yaml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
- GitHub Check: Check the WASM package and demo
- GitHub Check: Run tests under miri
- GitHub Check: Run rust tests (ubuntu-latest)
- GitHub Check: Run snippets and cpython tests (ubuntu-latest)
- GitHub Check: Run snippets and cpython tests on wasm-wasi
- GitHub Check: Check Rust code with rustfmt and clippy
- GitHub Check: Ensure compilation on various targets
🔇 Additional comments (1)
.github/workflows/ci.yaml (1)
281-282:Details
❓ Verification inconclusive
Remove macOS skips and run all platform-dependent tests
The updated step now excludes only platform‐independent tests without any macOS‐specific skips. Confirm that removing
$MACOS_SKIPSdoesn’t reintroduce hanging tests on both ARM and Intel macOS runners and that all previously skipped tests (test_configparser,test_socketserver) pass reliably.Please run:
and observe the CI results on both
macos-latest(ARM) and Intel images.
🏁 Script executed:
#!/usr/bin/env bash # Search for any remaining MACOS_SKIPS references rg -n 'MACOS_SKIPS' .Length of output: 21
No remaining
MACOS_SKIPSreferences foundI ran
rg -n 'MACOS_SKIPS' .and confirmed there are no matches in the codebase. All macOS skips have been removed.• Please verify that the CI on both ARM (
macos-latest) and Intel macOS runners completes without hanging and that previously skipped tests (e.g.test_configparser,test_socketserver) pass reliably.
🪧 Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>, please review it.Explain this complex logic.Open a follow-up GitHub issue for this discussion.
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. Examples:@coderabbitai explain this code block.@coderabbitai modularize this function.
- PR comments: Tag
@coderabbitaiin a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.@coderabbitai read src/utils.ts and explain its main purpose.@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.@coderabbitai help me debug CodeRabbit configuration file.
Support
Need help? Create a ticket on our support page for assistance with any issues or questions.
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (Invoked using PR comments)
@coderabbitai pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai generate docstringsto generate docstrings for this PR.@coderabbitai generate sequence diagramto generate a sequence diagram of the changes in this PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile to the root of your repository. - Please see the configuration documentation for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
- Visit our Documentation for detailed information on how to use CodeRabbit.
- Join our Discord Community to get help, request features, and share feedback.
- Follow us on X/Twitter for updates and announcements.