Build on Github Action test-macOS frequently fail due machine run out of disk space #3878
Comments
|
GitHub only offers 14 GB of storage on their "standard" runners: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories Unlike for Linux and Windows, GitHub do not offer more storage on their "large" (i.e. paid) runners (still 14 GB for macOS): https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners#specifications-for-general-larger-runners Apparently the amount of available disk space available decreased (albeit still with 14 GB available and therefore meeting GH's documented available storage) with GH's 20240827.4 macOS runner image -- there's a general discussion around this over in: actions/runner-images#10511 I'm aware of various hacks/scripts for the Ubuntu runners to reclaim space (see actions/runner-images#10386) but not for macOS. I do not know if there is anything we can do to reduce the size of Node.js macOS builds -- they appear to be significantly larger than their Linux equivalents. |
|
Should we disable macOS jobs for now? |
|
The problem is that we would have 0 CI coverage for arm64 macOS if we do it (Jenkins CI currently only tests on x64) |
|
Do we need Android sdk for macOS arm64 build? Any chance we can temporarily remove it (with a quick patch) from the |
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: nodejs#54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
|
Fixed by nodejs/node#54658 |
Refs: nodejs/build#3878 PR-URL: nodejs/node#54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: #54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: nodejs/node#54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> PR-URL: #182 Refs: nodejs/node#54658 Reviewed-By: Santiago Gimeno <[email protected]>
Refs: nodejs/build#3878 PR-URL: nodejs#54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Refs: nodejs/build#3878 PR-URL: nodejs#54658 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
The Github Actions start to fail frequently on test-macOS build step due to the current build on mac is about 18GB which seems more than the allocated disk space on the runner (14GB limit IIRC). See this for a failure example:
This currently impacts all the Pull Requests on nodejs cores.
The text was updated successfully, but these errors were encountered: