ci(pt_expt): cover torch.compile on a supported GPU release

Open
  • Is something wrong?
#5,935 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, pytorch
Domain
ci-cd, testing

Research direction

Start by locating the GPU CI configuration and the focused pt_expt compile tests, then inspect the shared compile-version gate used by #5913. Add coverage for at least one supported PyTorch release while retaining the PyTorch 2.10 eager CUDA job; done means the compile safeguards run on GPU CI without changing the global pin.

Written by the indexing model from the issue text.

Description

enhancement

Problem

The repository-wide GPU CI environment currently pins PyTorch 2.10, while the supported torch.compile releases are PyTorch 2.11 and 2.12, with PyTorch 2.13 support added by #5910. Consequently, pt_expt compile-only tests cannot run on GPU CI under a supported PyTorch release.

This supported-version GPU coverage gap predates #5913. That PR only makes the existing contract explicit by using the shared compile-version gate, so the PyTorch 2.10 CUDA job now skips compile-only tests instead of exercising an unsupported configuration.

The compile path has been manually validated on CUDA with PyTorch 2.11, 2.12, and 2.13. The repository-wide GPU pin cannot currently be raised because of unrelated CI compatibility issues, and changing that pin is outside the scope of #5913.

Desired coverage

  • Run the focused pt_expt compile tests on a GPU with at least one supported PyTorch release.
  • Exercise CUDA-specific compile safeguards such as forced int64 indexing and the constrained Triton tiling configuration.
  • Preserve the existing PyTorch 2.10 eager CUDA coverage until the unrelated CI blockers allow the global GPU pin to move.

Related

  • #5913
  • #5910
Dominant language
Python
Stars
2.1k
Forks
663
Avg merge
3d 11h
Merged PRs (30d)
25

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from deepmodeling/deepmd-kit

All issues in deepmodeling/deepmd-kit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.