Skip to content

run nightly-vs-upstream-main on 2.7.1 and multi-gpu also#2929

Merged
winglian merged 1 commit into
mainfrom
nightly-expansion
Jul 17, 2025
Merged

run nightly-vs-upstream-main on 2.7.1 and multi-gpu also#2929
winglian merged 1 commit into
mainfrom
nightly-expansion

Conversation

@winglian
Copy link
Copy Markdown
Collaborator

@winglian winglian commented Jul 16, 2025

manually triggered workflow:

Summary by CodeRabbit

  • Chores
    • Expanded nightly test coverage to include PyTorch 2.7.1 with CUDA 12.6.3 and Python 3.11.
    • Introduced additional nightly multi-GPU testing for select repository owners.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 16, 2025

Walkthrough

The nightly test workflow was updated to add a new test configuration for PyTorch 2.7.1 with CUDA 12.6.3 and Python 3.11. Additionally, a new job was introduced to run multi-GPU end-to-end tests using Modal, triggered only for a specific repository owner.

Changes

File(s) Change Summary
.github/workflows/tests-nightly.yml Added PyTorch 2.7.1/CUDA 12.6.3/Python 3.11 config to docker-e2e-tests matrix; introduced new docker-e2e-multigpu-tests job for multi-GPU Modal testing, conditional on repo owner.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Pre-commit
    participant Pytest
    participant Docker E2E Tests
    participant Docker E2E MultiGPU

    GitHub Actions->>Pre-commit: Run pre-commit checks
    Pre-commit->>Pytest: On success, run pytest
    Pytest->>Docker E2E Tests: On success, run docker-e2e-tests (matrix includes new config)
    Docker E2E Tests->>Docker E2E MultiGPU: On success, run docker-e2e-multigpu-tests (if owner matches)
    Docker E2E MultiGPU->>Modal: Launch cicd.multigpu test job
Loading

Suggested reviewers

  • djsaunde

Poem

In the warren of nightly tests we hop,
New configs and GPUs—oh, what a crop!
Modal magic, multi-GPU delight,
PyTorch and CUDA, running all night.
Rabbits rejoice, the matrix expands—
More tests, more carrots, for all our hands! 🥕✨


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.
    • 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.

Copy link
Copy Markdown
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

🧹 Nitpick comments (2)
.github/workflows/tests-nightly.yml (2)

142-144: Custom runner label modal trips action-lint
actionlint warns that modal is an unknown label.
If this is an internal self-hosted runner group, add it to .github/actionlint.yaml’s runnerLabels: allow-list to silence false positives and keep CI linting green.


158-181: High duplication between single- and multi-GPU jobs
docker-e2e-tests and docker-e2e-multigpu-tests share identical setup steps (checkout, Python, Modal install, env export). Consider extracting them into:

  1. A reusable workflow (.github/workflows/reusable-e2e.yml) invoked via uses:
  2. Or a composite action stored in .github/actions/setup-e2e.

This keeps the workflow DRY and reduces the risk of the two diverging.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 36cbe13 and 2d50bcb.

📒 Files selected for processing (1)
  • .github/workflows/tests-nightly.yml (2 hunks)
🧰 Additional context used
🪛 actionlint (1.7.7)
.github/workflows/tests-nightly.yml

143-143: label "modal" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)


170-170: property "axolotl_args" is not defined in object type {axolotl_extras: string; cuda: number; cuda_version: string; nightly_build: bool; num_gpus: number; python_version: number; pytorch: string}

(expression)

🔇 Additional comments (1)
.github/workflows/tests-nightly.yml (1)

109-115: 2.7.1 added only to E2E matrix – unit/CLI tests still pinned to ≤ 2.7.0
You extended the docker-e2e-tests matrix with PyTorch 2.7.1, but the upstream pytest job (line 29) still enumerates ["2.6.0", "2.7.0"].
If the intent is full coverage on 2.7.1, remember to bump that list as well; otherwise regressions might slip through unit tests while being caught (and diagnosed much later) in the slower E2E phase.

Comment on lines +170 to +177
run: |
echo "BASE_TAG=main-base-py${{ matrix.python_version }}-cu${{ matrix.cuda }}-${{ matrix.pytorch }}" >> $GITHUB_ENV
echo "PYTORCH_VERSION=${{ matrix.pytorch}}" >> $GITHUB_ENV
echo "AXOLOTL_ARGS=${{ matrix.axolotl_args}}" >> $GITHUB_ENV
echo "AXOLOTL_EXTRAS=${{ matrix.axolotl_extras}}" >> $GITHUB_ENV
echo "CUDA=${{ matrix.cuda }}" >> $GITHUB_ENV
echo "N_GPUS=${{ matrix.num_gpus }}" >> $GITHUB_ENV
echo "NIGHTLY_BUILD=${{ matrix.nightly_build }}" >> $GITHUB_ENV
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

matrix.axolotl_args is never defined – workflow will fail at run-time
Both E2E jobs export:

echo "AXOLOTL_ARGS=${{ matrix.axolotl_args }}" >> $GITHUB_ENV

Yet none of the matrix.include dictionaries declare an axolotl_args key.
GitHub Actions treats an undefined matrix property as a hard error (Context does not contain property 'axolotl_args'), so the job will exit before tests start.

Minimal fix – add an empty value to every matrix entry:

           num_gpus: 1
           axolotl_extras:
+          axolotl_args: ""
           nightly_build: "true"

…and similarly for the multi-GPU row.

🧰 Tools
🪛 actionlint (1.7.7)

170-170: property "axolotl_args" is not defined in object type {axolotl_extras: string; cuda: number; cuda_version: string; nightly_build: bool; num_gpus: number; python_version: number; pytorch: string}

(expression)

🤖 Prompt for AI Agents
In .github/workflows/tests-nightly.yml around lines 170 to 177, the matrix
property axolotl_args is used but not defined in any matrix.include entries,
causing a runtime error. To fix this, add an axolotl_args key with an empty
string value to every matrix.include dictionary where it is missing, ensuring
the property exists for all matrix configurations and prevents the workflow from
failing.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jul 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

@winglian winglian merged commit d2c3d5a into main Jul 17, 2025
18 of 20 checks passed
@winglian winglian deleted the nightly-expansion branch July 17, 2025 01:45
This was referenced Aug 26, 2025
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