Skip to content

[Inductor UT] Add expected failure for newly added case on XPU, align CUDA.#144457

Closed
etaf wants to merge 2 commits into
gh/etaf/86/basefrom
gh/etaf/86/head
Closed

[Inductor UT] Add expected failure for newly added case on XPU, align CUDA.#144457
etaf wants to merge 2 commits into
gh/etaf/86/basefrom
gh/etaf/86/head

Conversation

@etaf

@etaf etaf commented Jan 9, 2025

Copy link
Copy Markdown
Collaborator

@etaf etaf mentioned this pull request Jan 9, 2025
@pytorch-bot

pytorch-bot Bot commented Jan 9, 2025

Copy link
Copy Markdown

🔗 Helpful Links

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

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! (2 Unrelated Failures)

As of commit 5f11e42 with merge base 08eaaa6 (image):

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

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

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

@etaf etaf changed the title [Inductor UT] Add expected failure for newly added case on XPU, align [Inductor UT] Add expected failure for newly added case on XPU, align CUDA. Jan 9, 2025
@etaf etaf requested review from eellison and jansel January 9, 2025 06:35
@malfet malfet added the ciflow/xpu Run XPU CI tasks label Jan 9, 2025
@malfet

malfet commented Jan 9, 2025

Copy link
Copy Markdown
Contributor

@pytorchbot merge -f "Lint is green"

@pytorchmergebot

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

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

Merge failed

Reason: Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x 5a6695a0e90e7beb252e6a797174ab003a3ce5fd returned non-zero exit code 1

Auto-merging aten/src/ATen/native/mkldnn/xpu/Blas.cpp
CONFLICT (content): Merge conflict in aten/src/ATen/native/mkldnn/xpu/Blas.cpp
error: could not apply 5a6695a0e90... [XPU] Fix build error caused by incorrect namespace change by #144014
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Details for Dev Infra team Raised by workflow job

… XPU, align CUDA."


The newly added case `test_randint_distribution` from #143787 was set expected failure for CUDA but not for XPU.
 We add the expected failure here because if fails with the same reason as CUDA. 

cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang aakhundov

[ghstack-poisoned]
pytorchmergebot pushed a commit that referenced this pull request Jan 10, 2025
…144456)

Re-land #143975. Fix "cuda" hard code in test_pattern_matcher.py introduced by #139321
Fix #143974

Pull Request resolved: #144456
Approved by: https://github.com/EikanWang, https://github.com/malfet, https://github.com/jansel
ghstack dependencies: #144457
@github-actions github-actions Bot deleted the gh/etaf/86/head branch February 12, 2025 02:07
desai0007 pushed a commit to desai0007/test-repo-pytorch that referenced this pull request Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants