Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DISABLED test_comprehensive_gather_xpu_float32 (__main__.TestInductorOpInfoXPU) #152911

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
etaf opened this issue May 6, 2025 · 1 comment
Open
Labels
module: xpu Intel XPU related issues skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@etaf
Copy link
Collaborator

etaf commented May 6, 2025

Platforms: linux

This test was disabled because it is failing on main branch (recent examples).

cc @gujinghui @EikanWang @fengyuan14 @guangyey

@pytorch-bot pytorch-bot bot added the skipped Denotes a (flaky) test currently skipped in CI. label May 6, 2025
Copy link

pytorch-bot bot commented May 6, 2025

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:
  • Test name: test_comprehensive_gather_xpu_float32 (__main__.TestInductorOpInfoXPU)
  • Platforms for which to skip the test: linux
  • Disabled by etaf

Within ~15 minutes, test_comprehensive_gather_xpu_float32 (__main__.TestInductorOpInfoXPU) will be disabled in PyTorch CI for these platforms: linux. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #152911 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

@chuanqi129 chuanqi129 added the module: xpu Intel XPU related issues label May 6, 2025
@drisspg drisspg added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: xpu Intel XPU related issues skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests

3 participants