8000 Fix skipIfXpu and skipIfHpu disables tests when used on class by EikanWang · Pull Request #151315 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

Fix skipIfXpu and skipIfHpu disables tests when used on class #151315

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

Open
wants to merge 10 commits into
base: gh/EikanWang/80/base
Choose a base branch
from

Conversation

[ghstack-poisoned]
Copy link
pytorch-bot bot commented Apr 15, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ You can merge normally! (1 Unrelated Failure)

As of commit 4e82023 with merge base 032ef48 (image):

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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

@pytorch-bot pytorch-bot bot added ciflow/inductor module: inductor oncall: distributed Add this issue/PR to distributed oncall triage queue topic: not user facing topic category labels Apr 15, 2025
EikanWang added a commit that referenced this pull request Apr 15, 2025
ghstack-source-id: b08f834
Pull Request resolved: #151315
@EikanWang EikanWang changed the title Fix #150779 Fix skipIfXpu and skipIfHPU disables tests when used on class Apr 15, 2025
@EikanWang EikanWang changed the title Fix skipIfXpu and skipIfHPU disables tests when used on class Fix skipIfXpu and skipIfHPU disables tests when used on class Apr 15, 2025
@EikanWang EikanWang changed the title Fix skipIfXpu and skipIfHPU disables tests when used on class Fix skipIfXpu and skipIfHpu disables tests when used on class Apr 15, 2025
@EikanWang EikanWang requested a review from Copilot April 15, 2025 13:10
Copy link
Contributor
@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

test/distributed/test_functional_api.py:92

  • [nitpick] Consider adding a clear skip reason message to the unittest.skipIf decorators for HPU tests to improve readability and consistency with the XPU tests.
@unittest.skipIf(TEST_HPU)

Copy link
Contributor
@malfet malfet left a comment

Choose a reason for hiding this comment

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

Change looks reasonable to me(fix invocations though, i.e. failure are real), and please add a test plan. Also, if test class is multi-device, this decorator will skip CPU parts of it as well.

Also, removed "Fixes" as problem is not the actual use of the decorator, but the fact that this behavior is untested

@@ -90,7 +89,7 @@ def new_subgroups(group_size: int, pg_tag=None):
return cur_subgroup, subgroups


@skipIfHpu
@unittest.skipIf(TEST_HPU)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
@unittest.skipIf(TEST_HPU)
@unittest.skipIf(TEST_HPU, "Unsupported on HPU")

[ghstack-poisoned]
EikanWang added a commit that referenced this pull request Apr 16, 2025
ghstack-source-id: fa236d5
Pull Request resolved: #151315
@EikanWang
Copy link
Collaborator Author

I will submit another PR to refine the skipIfXpu decorator.

@EikanWang
Copy link
Collaborator Author
EikanWang commented Apr 16, 2025

@malfet, I just stacked another PR (#151420) to address the skipIfXpu issue regarding #15079.

@EikanWang EikanWang added the keep-going Don't stop on first failure, keep running tests until the end label Apr 16, 2025
[ghstack-poisoned]
@EikanWang
Copy link
Collaborator Author

By the way, @malfet , I'm fixing the CI failed test cases. When the CI signal is green, I will request your help in reviewing this PR again.

[ghstack-poisoned]
[ghstack-poisoned]
@EikanWang EikanWang requested a review from bdhirsh as a code owner April 16, 2025 13:59
@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@EikanWang
Copy link
Collaborator Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@Skylion007
Copy link
8000 Collaborator

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@cyyever
Copy link
Collaborator
cyyever commented Apr 30, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@EikanWang
Copy link
Collaborator Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/rem 9E88 otes/origin/viable/strict. Check the current status here

[ghstack-poisoned]
pytorchmergebot pushed a commit that referenced this pull request May 12, 2025
ghstack-source-id: a7a0ede
Pull Request resolved: #151315
@pytorchmergebot
Copy link
Collaborator

Successfully rebased gh/EikanWang/80/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/151315)

@EikanWang
Copy link
Collaborator Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@jeanschmidt
Copy link
Contributor

@pytorchbot revert -m "Seems to have introduced internal regressions, see D74668899. @malfet may you help the author get this PR merged?" -c ghfirst

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

pytorchmergebot added a commit that referenced this pull request May 14, 2025
…#151315)"

This reverts commit ee096b8.

Reverted #151315 on behalf of https://github.com/jeanschmidt due to Seems to have introduced internal regressions, see [D74668899](https://www.internalfb.com/diff/D74668899). @malfet may you help the author get this PR merged? ([comment](#151315 (comment)))
@pytorchmergebot
Copy link
Collaborator

@EikanWang your PR has been successfully reverted.

@pytorchmergebot pytorchmergebot added Reverted ci-no-td Do not run TD on this PR labels May 14, 2025
@EikanWang
Copy link
Collaborator Author

May I know the internal failures? So that I can refine this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-no-td Do not run TD on this PR ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request keep-going Don't stop on first failure, keep running tests until the end Merged module: inductor oncall: distributed Add this issue/PR to distributed oncall triage queue open source Reverted topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants
0