brain-score / brain-score/vision
Resolve Travis memory issues
Open
- Dominant language
- Python
- Stars
- 193
- Forks
- 105
- Avg merge
- 10h 48m
- Merged PRs (30d)
- 10
Description
Currently, when Travis runs out of resources, we either (a) restart the relevant test, (b) ignore the result, or (c) manually split the PR into smaller pieces. Is there a way to more elegantly handle travis running out or memory/disk space/log space so that it doesn't involve a human in the loop?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.