10000 [ROCm][CI] upgrade CI to ROCm 6.3 by jithunnair-amd · Pull Request #142152 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

[ROCm][CI] upgrade CI to ROCm 6.3 #142152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from
Closed

Conversation

jithunnair-amd
Copy link
Collaborator
@jithunnair-amd jithunnair-amd commented Dec 5, 2024

Copy link
pytorch-bot bot commented Dec 5, 2024

🔗 Helpful Links

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

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

❌ 13 New Failures, 2 Cancelled Jobs, 3 Unrelated Failures

As of commit 970a3dc with merge base 8d9ff9c (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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 ciflow/rocm Trigger "default" config CI on ROCm module: rocm AMD GPU support for Pytorch topic: not user facing topic category labels Dec 5, 2024
@jeffdaily
Copy link
Collaborator

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Tried to rebase and push PR #142152, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

@jeffdaily
Copy link
Collaborator

@pytorchbot rebase -b main

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

@jeffdaily jeffdaily marked this pull request as ready for review December 11, 2024 00:02
@jeffdaily jeffdaily requested review from a team and jeffdaily as code owners December 11, 2024 00:02
@jithunnair-amd jithunnair-amd added ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/inductor-rocm Trigger "inductor" config CI on ROCm labels Dec 12, 2024
@jeffdaily
Copy link
Collaborator

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

@jeffdaily
Copy link
Collaborator

@pytorchbot rebase -b main

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

@jeffdaily
Copy link
Collaborator

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

Copy link
Collaborator
@pruthvistony pruthvistony left a comment

Choose a reason for hiding this comment

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

LGTM

@jeffdaily
Copy link
Collaborator

@pytorchbot merge -f "ROCm-only changes to CI docker image and workflows; all ROCm tests passed; ignore all other failures as unrelated"

@pytorchmergebot
< 579F path d="M8 9a1.5 1.5 0 1 0 0-3 1.5 1.5 0 0 0 0 3ZM1.5 9a1.5 1.5 0 1 0 0-3 1.5 1.5 0 0 0 0 3Zm13 0a1.5 1.5 0 1 0 0-3 1.5 1.5 0 0 0 0 3Z"> Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/rocm Trigger "default" config CI on ROCm Merged module: rocm AMD GPU support for Pytorch open source topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0