Closed nightkr closed 3 weeks ago
So just compiling Trino itself seems to use around 10-12GB of space (sorry, didn't measure too accurately), which is just about brushing up against GitHub's 14GB limit.
One option would be to use a Large Runner, but in this case we seem to just about make it through the build itself, so we could "solve" it by deleting intermediate build products after the build.
Caused by #687, see https://github.com/stackabletech/docker-images/actions/runs/9546922567