You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: