[CUDA] Add serialTest decorator to largeTensorTest in test_cuda.py

[eqy]

Hopefully helps with disabled tests due to OOM such as #159069

cc @ptrblck @msaroufim @jerryzh168

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

❌ 1 Cancelled Job, 2 Unrelated Failures

As of commit b8d1ed2 with merge base e785c08 ():

CANCELLED JOB - The following job was cancelled. Please retry:

• trunk / linux-jammy-rocm-py3.10 / test (default, 2, 2, linux.rocm.gpu.2) (gh)
  ##[error]The operation was canceled.

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

• pull / linux-jammy-cuda12.8-py3.10-gcc11-test / test (distributed, 3, 3, linux.g4dn.12xlarge.nvidia.gpu) (gh) (disabled by #147754)
  distributed/test_c10d_functional_native.py::CompileTest::test_inductor_all_reduce_single

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / linux-jammy-py3_9-clang9-xla / test (xla, 1, 1, linux.12xlarge, unstable) (gh) (#158876)
  sccache: error: couldn't connect to server

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

[eqy]

@pytorchmergebot rebase

[pytorchmergebot]

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

[pytorchmergebot]

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

[eqy]

@pytorchmergebot merge

[pytorchmergebot]

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]

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.

[ngimel]

@pytorchbot merge -f "previous attempt timed out"

[pytorchmergebot]

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