Enable cache action for lint workflow

[huydhn]

Cache all python dependencies using GHA cache. I'm doing this for lint workflow first and will slowly roll it out to other workflows.

Testing

Before caching, pip cache is not found. Dependencies installation continues as usual:

After caching https://github.com/pytorch/pytorch/runs/8006214772?check_suite_focus=true. The long hash at the end of the cache key is the hash of requirements files

Note that the cache is in the runners themselves. This should be a transparent process.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 our office hours

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

✅ No Failures

As of commit 645b2ec:
💚 Looks good so far! There are no failures yet. 💚

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

[suo]

what's the expected impact on this change on TTS?

[huydhn]

what's the expected impact on this change on TTS?

Not much I think because installing dependencies isn't the long pole in term of TTS. However, it has a minor reliability boon that allows the cached copies to be used whenever there are upstream issues with pip. And the setup is pretty easy as you can see in the PR. Basically, we just need to add to setup-python

cache: pip
cache-dependency-path: requirements

[suo]

coolio

[malfet]

Looks good, but please avoid images in PR description, rather share link to respective runs + text-readable perf numbers

[huydhn]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here and land check progress here.
The merge job was triggered with the land checks (-l) flag. If you did not specify this flag yourself, you are likely enrolled in the land checks rollout. This means that your change will be merged once all checks on your PR and the land checks have passed (ETA 4 Hours). If you need to coordinate lands between different changes and cannot risk a land race, please add the ciflow/trunk label to your PR and wait for signal to complete, and then land your changes in proper order. Having trunk, pull, and Lint pre-run on a PR will bypass land checks and the ETA should be immediate. If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[github-actions]

Hey @huydhn.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

[malfet]

One needs to be careful with introducing new dependencies, as lint will fail for all users that have not rebased, as workflow definition is checked from master, but rest of the code is from PR, which results in the following failures:
https://github.com/pytorch/pytorch/runs/8020179452?check_suite_focus=true

[huydhn]

One needs to be careful with introducing new dependencies, as lint will fail for all users that have not rebased, as workflow definition is checked from master, but rest of the code is from PR, which results in the following failures: https://github.com/pytorch/pytorch/runs/8020179452?check_suite_focus=true

Note. In hindsight, I should have added the new file first, then made the change.