Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve Travis memory issues #862

Open
deirdre-k opened this issue May 24, 2024 · 0 comments
Open

Resolve Travis memory issues #862

deirdre-k opened this issue May 24, 2024 · 0 comments
Assignees

Comments

@deirdre-k
Copy link
Contributor

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?

@deirdre-k deirdre-k self-assigned this May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant