build 2.7.1 images and ci

[winglian]

Description

Motivation and Context

How has this been tested?

Screenshots (if appropriate)

Types of changes

Social Handles (Optional)

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflows to use PyTorch version 2.7.1 instead of 2.7.0 for relevant test and build jobs.

[coderabbitai]

Walkthrough

The changes update GitHub Actions workflow files to use PyTorch version 2.7.1 instead of 2.7.0 across various build and test matrix configurations, including CUDA environments. No modifications were made to workflow logic, steps, or environment variables beyond this version bump.

Changes

Files	Change Summary
.github/workflows/main.yml	Updated PyTorch version from 2.7.0 to 2.7.1 in matrix for CUDA 12.6.3 and 12.8.1 for build jobs.
.github/workflows/multi-gpu-e2e.yml	Changed PyTorch version from 2.7.0 to 2.7.1 for CUDA 12.6.3 with Python 3.11 in test matrix.
.github/workflows/tests.yml	Replaced all PyTorch 2.7.0 occurrences with 2.7.1 in pytest, pytest-sdist, and docker-e2e-tests matrices.

Suggested labels

ready to merge

Suggested reviewers

• djsaunde
• NanoCode012

Poem

A version bump, a hop, a leap,
PyTorch now is less asleep!
From 2.7.0 to .1 we go,
Workflows updated, smooth as snow.
The CI bunnies dance with glee—
More tests to run, more code to see!
🐇✨

---

📜 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 581dd32 and 74110d8.

📒 Files selected for processing (3)

• .github/workflows/main.yml (2 hunks)
• .github/workflows/multi-gpu-e2e.yml (1 hunks)
• .github/workflows/tests.yml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: PyTest from Source Dist (3.11, 2.7.1)
• GitHub Check: PyTest from Source Dist (3.11, 2.6.0)
• GitHub Check: PyTest from Source Dist (3.11, 2.5.1)
• GitHub Check: PyTest (3.11, 2.5.1)
• GitHub Check: PyTest (3.11, 2.7.1)
• GitHub Check: PyTest (3.11, 2.6.0)
• GitHub Check: test-axolotl-multigpu (124, 12.4.1, 3.11, 2.5.1, 2, true)
• GitHub Check: test-axolotl-multigpu (126, 12.6.3, 3.11, 2.7.1, 2, true)
• GitHub Check: test-axolotl-multigpu (124, 12.4.1, 3.11, 2.6.0, vllm, 2, true)
• GitHub Check: pre-commit

🔇 Additional comments (9)

.github/workflows/multi-gpu-e2e.yml (1)

46-46: Bump PyTorch to 2.7.1 for CUDA 12.6.3. Aligns multi-GPU E2E tests with other workflows.

.github/workflows/main.yml (4)

32-32: Bump PyTorch to 2.7.1 for CUDA 12.6.3 build. Ensures consistency with multi-GPU and test workflows.

---

37-37: Bump PyTorch to 2.7.1 for CUDA 12.8.1 build. Aligns with other build matrices.

---

100-100: Bump PyTorch to 2.7.1 for CUDA 12.6.3 in cloud build. Matches core build matrix.

---

105-105: Bump PyTorch to 2.7.1 for CUDA 12.8.1 in cloud build. Consistent with other jobs.

.github/workflows/tests.yml (4)

55-55: Add PyTorch 2.7.1 to PyTest matrix. Ensures unit tests cover the new version.

---

128-128: Add PyTorch 2.7.1 to source-dist PyTest matrix. Maintains test coverage for the new release.

---

265-265: Bump PyTorch to 2.7.1 for CUDA 12.6.3 in Docker E2E tests. Aligns test matrix with updated build configs.

---

271-271: Bump PyTorch to 2.7.1 for CUDA 12.8.1 in Docker E2E tests. Consistent with updated build configurations.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @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 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 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]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!