fix: failing gh actions due to runner out of disk space #7565
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
backend_test cache node modules step failing due to out of memory: cache lookup restores the tar file in memory, but when unzipped to storage, out of disk space memory occurs. This causes all our github actions to fail.
The error message is the github runnner running out of disk storage space when extracting the restored cached tar file.
Fix:
Remove the code to generate swapfile since it is no longer needed.
Explanation:
running
df -h
shows we have 19GB of disk space (despite 14GB indicated by github). We previously allocate 15GB to swapfile, leaving 4GB for storage.Recently, the disk space usage has likely exceeded the 4GB and hence caused this OO disk space error.
Since GH runners now provide 16GB of memory instead of the previous 7GB, we do not need to manually add this swapfile any more.
Additional context:
From @g-tejas using wayback machine:
![image](https://private-user-images.githubusercontent.com/55353265/355021761-1473a6e8-c100-4027-a581-7daeb9372317.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM1NTk4MDEsIm5iZiI6MTcyMzU1OTUwMSwicGF0aCI6Ii81NTM1MzI2NS8zNTUwMjE3NjEtMTQ3M2E2ZTgtYzEwMC00MDI3LWE1ODEtN2RhZWI5MzcyMzE3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODEzVDE0MzE0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTUxMTQxNTkwZGIyN2E0YTZkMzA1MTAzMzE4NzAwMTk4ZjUxOGRmNGY0MmUzZGNhYzBhNDllMTAxMTg1YjMyNjgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0._KnwfTSr7Nm9cWdyMEmBI85IZOL_yCZ1dRMTrHaLnXI)
back when swap file of 15G was selected, there was only 7GB of RAM allocated to standard github runners. Today, there is 16GB allocated to standard github runners. Hence, we do not need the extra RAM for github runner.