Disable failing GPU unit test

[atalman]

Disable failing GPU unit test.
See associated issue: #3376

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure

As of commit 233e462:

NEW FAILURE - The following job has failed:

• build (3.8) (gh)

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

[mthrok]

Thanks for looking into this.

Instead of disabling each of them, can we introduce a common decorator and environment variable so that when we want to check which one is temporary disabled, we can just flip the env var in CI and see which one fails?

https://github.com/pytorch/audio/blob/main/test/torchaudio_unittest/common_utils/case_utils.py#L280-L284

disabledInCI = _skipIf(
    "CI" in os.environ,
    reason="Tests are failing on CI consistently. Disabled while investigating.",
    key="TEMPORARY_DISABLED",
)

and

export TORCHAUDIO_TEST_ALLOW_SKIP_IF_ TEMPORARY_DISABLED=1

This will skip those decorated with disabledInCI in CI, but will fail in local env.

[facebook-github-bot]

@atalman has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@atalman merged this pull request in caf3ac0.

[github-actions]

Hey @atalman.
You merged this PR, but labels were not properly added. Please add a primary and secondary label (See https://github.com/pytorch/audio/blob/main/.github/process_commit.py).

---

Some guidance:

Use 'module: ops' for operations under 'torchaudio/{transforms, functional}', and ML-related components under 'torchaudio/csrc' (e.g. RNN-T loss).

Things in "examples" directory:

• 'recipe' is applicable to training recipes under the 'examples' folder,
• 'tutorial' is applicable to tutorials under the “examples/tutorials” folder
• 'example' is applicable to everything else (e.g. C++ examples)
• 'module: docs' is applicable to code documentations (not to tutorials).
  Regarding examples in code documentations, please also use 'module: docs'.

Please use 'other' tag only when you’re sure the changes are not much relevant to users, or when all other tags are not applicable. Try not to use it often, in order to minimize efforts required when we prepare release notes.

---

When preparing release notes, please make sure 'documentation' and 'tutorials' occur as the last sub-categories under each primary category like 'new feature', 'improvements' or 'prototype'.

Things related to build are by default excluded from the release note, except when it impacts users. For example:
* Drop support of Python 3.7.
* Add support of Python 3.X.
* Change the way a third party library is bound (so that user needs to install it separately).