meta-pytorch / meta-pytorch/data
Address CI issues related to GDrive download quota
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 179
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 2
Description
🚀 The feature
Mitigate false positive test failures related to Google Drive. Some possible solutions are:
- Move the files to a location that is still on GDrive but has a higher daily download quota (or no quota at all)
- We can also use different files that are already in such GDrive location.
- Make a request to third-party to life the quota for particular files
Motivation, pitch
Within the tests that have the decorator @slow (i.e. tests triggered by Github label "ciflow/slow"), a few of them connect to Google Drive to download files in order to test our DataPipes' functionalities. These tests occasionally fail because of issues related to download quota and not because of a bug in our implementation.
Alternatives
Change our tests/codes to ignore these cases, but that may just end up not testing the functionalities that we want to test.
Examples
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tests marked by the @slow decorator and the linked GitHub Actions CI failure. Trace which Google Drive downloads are quota-sensitive and choose a supported mitigation that preserves the intended DataPipes coverage. Done means the slow tests no longer fail falsely because of Google Drive download quota.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100