Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

DISABLED test_aliased_param_return_cpu (__main__.CpuTests) #103466

Closed
eellison opened this issue Jun 12, 2023 · 3 comments
Closed

DISABLED test_aliased_param_return_cpu (__main__.CpuTests) #103466

eellison opened this issue Jun 12, 2023 · 3 comments
Labels
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

@eellison
Copy link
Contributor

馃悰 Describe the bug

failing on hud

Versions

master

@pytorch-bot pytorch-bot bot added the skipped Denotes a (flaky) test currently skipped in CI. label Jun 12, 2023
@pytorch-bot
Copy link

pytorch-bot bot commented Jun 12, 2023

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_aliased_param_return_cpu (__main__.CpuTests)
  • Platforms for which to skip the test: none parsed, defaulting to ALL platforms
  • Disabled by eellison

Within ~15 minutes, test_aliased_param_return_cpu (__main__.CpuTests) will be disabled in PyTorch CI for all platforms. 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, win, windows.

@mikaylagawarecki mikaylagawarecki added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 13, 2023
@mikaylagawarecki
Copy link
Contributor

Seems like PR that added this test above was reverted, should this be closed?

@eellison
Copy link
Contributor Author

Yea, the test is explicitly skipped now. can close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

2 participants