[Nova] Windows CPU Unittests on Nova

[osalpekar]

Continuing with the job migrations from CCI to Nova, this PR introduces the Windows CPU Unittest job as a Nova workflow.

The job is passing: https://github.com/pytorch/audio/actions/runs/5094569687/jobs/9159020192?pr=3329.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 5c0a764:

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]

Q: Which dependency requires this?

[osalpekar]

pytorch-lightning depends on fsspec. Installing pytorch-lightning fails on windows in the GHA env due to SSL cert issues, but this fixes the issue.

[mthrok]

I think it's more useful to mention why it was broken.
And the reason is because somehow compiling KenLm on Windows stopped working for a part that is not changed for 10 years.

[osalpekar]

Thanks for the added context - I'll append this comment

[osalpekar]

The fixes in #3378 and #3381 made the unittests work on trunk again with kenlm. I brought this dependency back in the Nova job as well.

[osalpekar]

The job is now passing: https://github.com/pytorch/audio/actions/runs/5094569687/jobs/9159020192?pr=3329.

[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 6425d46.

[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).