-
Notifications
You must be signed in to change notification settings - Fork 80
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
Re-enable py-client-ticking tests #5899
Comments
From Colin: https://github.com/jlumbroso/free-disk-space as potential ways to clean up at a runner environment level if necessary. |
The actual test image being created ( The entrypoint code doesn't seem to be that big either:
|
The bigger culprit may be the image builder image:
|
It's possible that we've relied on >14GB of disk space, and just more recently, GH CI has reduced the amount of disk space: |
This removes unneeded data from the CI runner to free up extra disk space using https://github.com/jlumbroso/free-disk-space. An emphasis has been placed on the speed of removal, and as such, a few of the defaults have been changed. Namely, docker image deletion and large misc packages have been explicitly set to false (as they are more complex than a simple `rm`). The tool cache deletion has also been set to false, as we might take advantage of that for java. Fixes deephaven#5899
py-client-ticking tests were disabled in #5893 due to CI disk space related failures; it's conceivable that py-client-ticking isn't to blame, and it's just the straw that breaks CIs disk. We should do further investigation into the amount of disk space used in CI in general and proceed as appropriate; to either reduce disk space across a wider range of tasks, or reduce the disk space of py-client-ticking tests if it is to blame.
The text was updated successfully, but these errors were encountered: