Skip to content

Migrate pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc11 -> pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc13#157748

Closed
atalman wants to merge 6 commits intopytorch:mainfrom
atalman:update_gcc11
Closed

Migrate pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc11 -> pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc13#157748
atalman wants to merge 6 commits intopytorch:mainfrom
atalman:update_gcc11

Conversation

@atalman
Copy link
Copy Markdown
Contributor

@atalman atalman commented Jul 7, 2025 •
edited
Loading

Binary builds where migrated to gcc13 a while ago: #152825
This migrates pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc11 jobs to pytorch-linux-jammy-cuda12.8-cudnn9-py3-gcc13. Make sure we have a coverage for GCC13 in CI

Reference issue, users seeing regression with gcc13: #157626

@atalman atalman requested review from a team and jeffdaily as code owners July 7, 2025 23:48
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Jul 7, 2025 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/157748

Note: Links to docs will display an error until the docs builds have been completed.

❌ 13 New Failures, 14 Unrelated Failures

As of commit 025f869 with merge base 288bf54 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot Bot added the topic: not user facing topic category label Jul 7, 2025
huydhn
huydhn approved these changes Jul 7, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@huydhn huydhn left a comment

Choose a reason for hiding this comment

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

LGTM!

@atalman atalman added ciflow/trunk Trigger trunk jobs on your pull request ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/slow ciflow/inductor labels Jul 7, 2025
@robert-hardwick
Copy link
Copy Markdown
Collaborator

robert-hardwick commented Jul 8, 2025 •
edited
Loading

Do you plan to migrate aarch64 ci image as a separate PR?

@atalman
Copy link
Copy Markdown
Contributor Author

atalman commented Jul 8, 2025

HI @robert-hardwick yes. Will try to migrate CI step by step. This way its easier to deal with errors we see in CI

@robert-hardwick robert-hardwick mentioned this pull request Jul 11, 2025
Closed
@atalman
Copy link
Copy Markdown
Contributor Author

atalman commented Jul 12, 2025

@pytorchmergebot rebase -b main

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

pytorchmergebot commented Jul 12, 2025

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

pytorchmergebot commented Jul 12, 2025

Successfully rebased update_gcc11 onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout update_gcc11 && git pull --rebase)

@atalman
Copy link
Copy Markdown
Contributor Author

atalman commented Jul 16, 2025

@pytorchmergebot rebase -b main

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

pytorchmergebot commented Jul 16, 2025

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

pytorchmergebot commented Jul 16, 2025

Rebase failed due to Command git -C /home/runner/work/pytorch/pytorch rebase refs/remotes/origin/main pull/157748/head returned non-zero exit code 1

Rebasing (1/6)
Rebasing (2/6)
Auto-merging .github/workflows/periodic.yml
CONFLICT (content): Merge conflict in .github/workflows/periodic.yml
error: could not apply 9db122135b0... fix
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Could not apply 9db122135b0... # fix

Raised by https://github.com/pytorch/pytorch/actions/runs/16332182309

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Sep 15, 2025

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions Bot added the Stale label Sep 15, 2025
@github-actions github-actions Bot closed this Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@huydhn huydhn huydhn approved these changes

@malfet malfet malfet approved these changes

@jeffdaily jeffdaily Awaiting requested review from jeffdaily

Assignees

No one assigned

Labels

ciflow/inductor ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/slow ciflow/trunk Trigger trunk jobs on your pull request Stale topic: not user facing topic category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@atalman @robert-hardwick @pytorchmergebot @huydhn @malfet