Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[r2] CI: fix Python workflow #4364

Merged
merged 2 commits into from
Nov 15, 2024
Merged

Conversation

njzjz
Copy link
Member

@njzjz njzjz commented Nov 15, 2024

Summary by CodeRabbit

  • Chores
    • Updated the workflow configuration for testing Python dependencies to improve clarity and installation steps.
    • Adjusted installation commands for mpi4py and horovod to streamline the process.

Signed-off-by: Jinzhe Zeng <[email protected]>
Copy link
Contributor

coderabbitai bot commented Nov 15, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request modifies the workflow configuration for testing Python in the .github/workflows/test_python.yml file. It adjusts the installation steps for dependencies, particularly focusing on the installation of mpi4py and horovod. The tf field for Python versions 3.8 and 3.12 is left empty, indicating no TensorFlow specification. The installation command for mpi4py has been separated from horovod, with the latter now installed using the --no-build-isolation flag when the tf variable is empty. Environment variables for horovod remain unchanged.

Changes

File Change Summary
.github/workflows/test_python.yml Modified installation steps for dependencies; separated mpi4py and horovod installation commands; retained environment variables for horovod.

Possibly related PRs

  • ci: speed up Python test  #3776: The changes in this PR also involve modifications to the .github/workflows/test_python.yml file, specifically related to the installation of mpi4py and horovod, which aligns with the changes made in the main PR regarding the installation commands for these packages.
  • CI: set --clean-durations for pytest-split #4341: This PR updates the .github/workflows/test_python.yml file as well, focusing on the pytest command and duration management, which may relate to the overall workflow structure and testing process addressed in the main PR.

Suggested reviewers

  • wanghan-iapcm

Warning

Rate limit exceeded

@njzjz has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d4fb0e5 and 92599c9.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d4fb0e5 and 92599c9.

📒 Files selected for processing (1)
  • .github/workflows/test_python.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/test_python.yml

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in 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 generate unit testing code.
    • @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.

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 pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 440bb82 and d4fb0e5.

📒 Files selected for processing (1)
  • .github/workflows/test_python.yml (1 hunks)
🔇 Additional comments (1)
.github/workflows/test_python.yml (1)

37-39: Verify the necessity of separate mpi4py installation

Let's understand if this change was introduced to fix specific CI issues.

Run the following script to check recent workflow runs and issues:

✅ Verification successful

Separate mpi4py installation is necessary for proper dependency resolution

The separate installation of mpi4py before horovod is a valid change because:

  1. The git history shows this change was specifically introduced to handle dependency resolution issues
  2. The workflow uses OpenMPI (setup-mpi action) which requires proper mpi4py installation
  3. Installing mpi4py separately first ensures it's properly linked with the system MPI before horovod installation
  4. The --no-build-isolation flag is used only for horovod, indicating potential build conflicts when installed together
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check workflow history and related issues for context

# Check recent workflow runs for this file
gh run list --workflow=test_python.yml --limit 5 --json conclusion,createdAt,headBranch

# Search for related issues mentioning mpi4py or horovod installation problems
gh issue list --search "mpi4py horovod in:title,body" --state all --limit 5 --json number,title,state

Length of output: 973


Script:

#!/bin/bash
# Check the git history of the file to understand when and why these changes were introduced
git log -p .github/workflows/test_python.yml | grep -A 20 "mpi4py"

# Check if there are any other workflow files or installation scripts that handle mpi4py or horovod
fd -e yml -e yaml -e sh | xargs grep -l "mpi4py\|horovod"

# Look at the content of the installation script
cat source/install/uv_with_retry.sh

Length of output: 3145

.github/workflows/test_python.yml Outdated Show resolved Hide resolved
Copy link

codecov bot commented Nov 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.03%. Comparing base (440bb82) to head (92599c9).
Report is 1 commits behind head on r2.

Additional details and impacted files
@@             Coverage Diff             @@
##               r2    #4364       +/-   ##
===========================================
+ Coverage   62.75%   78.03%   +15.27%     
===========================================
  Files         164      342      +178     
  Lines       19147    33851    +14704     
  Branches     2863     2876       +13     
===========================================
+ Hits        12016    26416    +14400     
- Misses       6690     6692        +2     
- Partials      441      743      +302     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@njzjz njzjz requested a review from Copilot November 15, 2024 19:36

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.

@njzjz njzjz marked this pull request as ready for review November 15, 2024 21:01
@njzjz njzjz merged commit aef3532 into deepmodeling:r2 Nov 15, 2024
40 of 46 checks passed
@njzjz njzjz deleted the r2-fix-python-workflow branch November 15, 2024 21:04
This was referenced Nov 25, 2024
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