Skip to content

Conversation

@njzjz
Copy link
Member

@njzjz njzjz commented May 1, 2025

PyTorch 2.7 used _GLIBCXX_USE_CXX11_ABI=1, so there is no block to enable USE_PT_PYTHON_LIBS.

Summary by CodeRabbit

  • Chores
    • Simplified workflow setup by installing PyTorch via pip instead of manual libtorch downloads and environment variable configuration.
    • Removed explicit libtorch directory handling in build and test workflows.
  • Documentation
    • Updated installation guide to remove ABI compatibility warnings for PyTorch and clarified build option usage.
  • Refactor
    • Adjusted build scripts to enable use of PyTorch Python libraries during the build process.

Copilot AI review requested due to automatic review settings May 1, 2025 17:19
@njzjz njzjz added the Test CUDA Trigger test CUDA workflow label May 1, 2025
@github-actions github-actions bot added Docs and removed Test CUDA Trigger test CUDA workflow labels May 1, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the CI pipelines and installation documentation to switch from downloading a standalone libtorch package to using the pip‐installed torch (version 2.7 or higher).

  • Updated installation instructions in the docs to remove the outdated ABI compatibility note.
  • Modified several GitHub workflows (test_cuda, test_cc, codeql, build_cc) to pip install torch instead of downloading libtorch and to remove now-unnecessary environment variable settings.

Reviewed Changes

Copilot reviewed 5 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
File Description
doc/install/install-from-source.md Removed warning about _GLIBCXX_USE_CXX11_ABI to reflect PyTorch 2.7's settings.
.github/workflows/test_cuda.yml Removed libtorch download and environment variable settings; now uses pip-installed torch.
.github/workflows/test_cc.yml Eliminated libtorch download and its related environment setup, replacing it with pip install of torch.
.github/workflows/codeql.yml Removed libtorch download steps and the export of libtorch paths, now relying on pip install of torch.
.github/workflows/build_cc.yml Updated to use pip installation of torch and removed outdated environment variable assignments referencing libtorch.
Files not reviewed (2)
  • source/install/build_cc.sh: Language not supported
  • source/install/test_cc_local.sh: Language not supported
Comments suppressed due to low confidence (4)

.github/workflows/test_cuda.yml:82

  • [nitpick] Consider adding a comment explaining the removal of libtorch from LD_LIBRARY_PATH to clarify the transition to using the pip-installed torch package.
export LD_LIBRARY_PATH=$CUDA_PATH/lib64:/usr/lib/x86_64-linux-gnu/:$GITHUB_WORKSPACE/dp_test/lib:$GITHUB_WORKSPACE/libtorch/lib:$LD_LIBRARY_PATH

.github/workflows/test_cc.yml:62

  • [nitpick] Consider adding a comment to clarify that the removal of libtorch from LD_LIBRARY_PATH is intentional, given that the pip-installed torch manages library paths differently.
LD_LIBRARY_PATH: ${{ github.workspace }}/dp_test/lib:${{ github.workspace }}/libtorch/lib

.github/workflows/codeql.yml:54

  • [nitpick] Consider including a comment to explain the removal of libtorch-related environment settings and to note the reliance on the pip-installed torch package.
export CMAKE_PREFIX_PATH=$GITHUB_WORKSPACE/libtorch

.github/workflows/build_cc.yml:65

  • [nitpick] Consider documenting the rationale for removing libtorch path assignments in favor of the pip-installed torch, to ease future maintenance.
export CMAKE_PREFIX_PATH=$GITHUB_WORKSPACE/libtorch

@njzjz njzjz added the Test CUDA Trigger test CUDA workflow label May 1, 2025
@github-actions github-actions bot removed the Test CUDA Trigger test CUDA workflow label May 1, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 1, 2025

📝 Walkthrough

"""

Walkthrough

This update modifies the build, test, and analysis workflows as well as documentation and build scripts related to PyTorch integration. The workflows now install PyTorch via pip (version 2.7 or higher) instead of downloading and extracting the libtorch C++ distribution. Environment variables and steps referencing the local libtorch directory have been removed. Build scripts are updated to use the -D USE_PT_PYTHON_LIBS=TRUE CMake option, enabling usage of PyTorch Python libraries. Documentation is simplified by removing an ABI compatibility warning regarding PyTorch PyPI packages.

Changes

Files/Paths Change Summary
.github/workflows/build_cc.yml, .github/workflows/test_cc.yml, .github/workflows/test_cuda.yml, .github/workflows/codeql.yml Replaced manual libtorch download/unzip with pip install torch>=2.7 from PyTorch CPU wheels; removed CMAKE_PREFIX_PATH and libtorch-specific env vars.
source/install/build_cc.sh, source/install/test_cc_local.sh Added -D USE_PT_PYTHON_LIBS=TRUE to CMake options in build/test scripts.
doc/install/install-from-source.md Removed ABI compatibility warning for PyTorch PyPI packages; simplified build instructions for PyTorch backend.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant pip
    participant BuildScript
    participant CMake
    participant PyTorchPythonLibs

    Workflow->>pip: Install torch>=2.7 from PyTorch CPU wheels
    Workflow->>BuildScript: Run build_cc.sh/test_cc_local.sh
    BuildScript->>CMake: Configure with -D USE_PT_PYTHON_LIBS=TRUE
    CMake->>PyTorchPythonLibs: Use PyTorch Python libraries for build
Loading

Possibly related PRs

Suggested labels

Core, Python, C++

Suggested reviewers

  • wanghan-iapcm
    """

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 932cabc and a2e68d5.

📒 Files selected for processing (3)
  • .github/workflows/build_cc.yml (1 hunks)
  • .github/workflows/codeql.yml (1 hunks)
  • .github/workflows/test_cc.yml (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • .github/workflows/codeql.yml
  • .github/workflows/build_cc.yml
  • .github/workflows/test_cc.yml
⏰ Context from checks skipped due to timeout of 90000ms (22)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Build C library (2.14, >=2.5.0rc0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
  • GitHub Check: Analyze (c-cpp)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Test Python and C++ on CUDA

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.

❤️ 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.

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 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@codecov
Copy link

codecov bot commented May 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.81%. Comparing base (99c9dc2) to head (a2e68d5).
⚠️ Report is 77 commits behind head on devel.

Additional details and impacted files
@@           Coverage Diff           @@
##            devel    #4720   +/-   ##
=======================================
  Coverage   84.80%   84.81%           
=======================================
  Files         696      696           
  Lines       67264    67263    -1     
  Branches     3541     3540    -1     
=======================================
  Hits        57046    57046           
+ Misses       9085     9084    -1     
  Partials     1133     1133           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@njzjz njzjz requested a review from wanghan-iapcm May 2, 2025 04:58
@wanghan-iapcm wanghan-iapcm added this pull request to the merge queue May 6, 2025
Merged via the queue into deepmodeling:devel with commit 01c3c16 May 6, 2025
61 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants