XComp opened a new pull request, #24277: URL: https://github.com/apache/flink/pull/24277
## What is the purpose of the change There was a drop in disk space some time between Feb 2 and Feb 3. Previously, the runners had a disk size of ~84G. That dropped to ~73G. Instead of 24G free space, the e2e tests were only able to use 14G. This seems to be a GHA runner specific issue. The Azure Pipeline runners have a disk size of 73G as well, but come with less disk being used from the start. That is why we're not seeing the issue in Azure Pipelines. There are some binaries which we're not really using. Removing those would already free quite some disk space: * Andoid: ~9G * CodeQL: ~5G * .NET: ~1G Removing these binaries results in another 15G of additional space. There is a risk that GitHub Action requires some of these dependencies, though. But for this change, I got inspired by [easymon/maximize-build-space:action.yml](https://github.com/easimon/maximize-build-space/blob/master/action.yml]. That plugin does exactly that (+ some other even more elaborate things like creating a LVM volumes). I didn't use the plugin itself because I wanted to keep the impact on the runner as small as possible. Just removing the files seems to be the easiest way to gain some disk space. ## Brief change log * Adds step to `job_init` action that deletes the folders for Android, CodeQL and .NET and logs the disk space afterwards ## Verifying this change * The e2e tests should succeed again * No instabilities should appear due to the missing binaries ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
