Skip to content

Build on Github Action test-macOS frequently fail due machine run out of disk space #3878

Closed

Description

@jakecastelli

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:

test-macOS
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 47 MB

This currently impacts all the Pull Requests on nodejs cores.

Activity

  1. richardlau commented on Aug 30, 2024

    @richardlau
    Member

    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.

  2. targos commented on Aug 30, 2024

    @targos
    Member

    Should we disable macOS jobs for now?

  3. targos commented on Aug 30, 2024

    @targos
    Member

    The problem is that we would have 0 CI coverage for arm64 macOS if we do it (Jenkins CI currently only tests on x64)

  4. jakecastelli commented on Aug 30, 2024

    @jakecastelli
    MemberAuthor

    Do we need Android sdk for macOS arm64 build? Any chance we can temporarily remove it (with a quick patch) from the test-macOS job? seems like it can claim back ~12GB storage space.

  5. targos commented on Sep 1, 2024

    @targos
    Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions