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

ci: install GPU JAX in GPU CI #4293

Merged
merged 1 commit into from
Nov 2, 2024
Merged

Conversation

njzjz
Copy link
Member

@njzjz njzjz commented Oct 31, 2024

Summary by CodeRabbit

  • Chores
    • Updated the workflow configuration for testing CUDA to improve efficiency and concurrency.
    • Added a new package for enhanced environment setup in CUDA testing.
    • Introduced an environment variable to optimize GPU memory allocation during tests.

@njzjz njzjz added the Test CUDA Trigger test CUDA workflow label Oct 31, 2024
Copy link
Contributor

coderabbitai bot commented Oct 31, 2024

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the GitHub Actions workflow for testing CUDA. It adds a merge_group trigger to enable concurrent workflow execution and refines the if condition for the test_cuda job to accommodate this new event. Additionally, the installation command for Python dependencies now includes the jax[cuda12] package, and an environment variable XLA_PYTHON_CLIENT_PREALLOCATE is set to false for better GPU memory management during testing.

Changes

File Change Summary
.github/workflows/test_cuda.yml - Added merge_group trigger for concurrent execution.
- Refined if condition for test_cuda job.
- Included jax[cuda12] in Python dependencies.
- Introduced XLA_PYTHON_CLIENT_PREALLOCATE environment variable set to false.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant CUDA Environment

    User->>GitHub Actions: Trigger merge_group event
    GitHub Actions->>CUDA Environment: Run test_cuda job
    CUDA Environment->>CUDA Environment: Install jax[cuda12]
    CUDA Environment->>CUDA Environment: Set XLA_PYTHON_CLIENT_PREALLOCATE=false
    CUDA Environment->>GitHub Actions: Execute tests
    GitHub Actions->>User: Return test results
Loading

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: 0

🧹 Outside diff range and nitpick comments (1)
.github/workflows/test_cuda.yml (1)

50-50: Consider pinning the JAX version for better reproducibility.

While tensorflow and torch versions are pinned, the JAX version is not. This could lead to unexpected behavior if JAX releases a breaking change.

Consider updating to:

-    - run: source/install/uv_with_retry.sh pip install --system "tensorflow~=2.18.0rc2" "torch~=2.5.0" "jax[cuda12]"
+    - run: source/install/uv_with_retry.sh pip install --system "tensorflow~=2.18.0rc2" "torch~=2.5.0" "jax[cuda12]~=0.4.23"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9c767ad and e92b989.

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

64-65: LGTM! Well-documented memory management configuration.

Setting XLA_PYTHON_CLIENT_PREALLOCATE=false is a good practice for CI environments to prevent JAX from pre-allocating all GPU memory. The documentation reference is helpful for future maintenance.


Line range hint 19-20: Verify CUDA version compatibility across dependencies.

There's a minor version mismatch in CUDA versions:

  • Container uses CUDA 12.3.1
  • PyTorch is downloaded with CUDA 12.4
  • JAX is installed with CUDA 12 support

While minor version differences might work, it's better to align all versions for consistency.

Also applies to: 50-50, 71-72

🧰 Tools
🪛 actionlint

51-51: shellcheck reported issue in this script: SC2155:warning:1:8: Declare and assign separately to avoid masking return values

(shellcheck)


51-51: shellcheck reported issue in this script: SC2155:warning:2:8: Declare and assign separately to avoid masking return values

(shellcheck)


51-51: shellcheck reported issue in this script: SC2102:info:3:61: Ranges can only match single chars (mentioned due to duplicates)

(shellcheck)

@github-actions github-actions bot removed the Test CUDA Trigger test CUDA workflow label Oct 31, 2024
@wanghan-iapcm wanghan-iapcm added this pull request to the merge queue Nov 2, 2024
Merged via the queue into deepmodeling:devel with commit f129cff Nov 2, 2024
54 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.

2 participants