Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runner is shutdown due to excessive resource usage #758

Closed
Enchufa2 opened this issue Sep 9, 2023 · 3 comments
Closed

Runner is shutdown due to excessive resource usage #758

Enchufa2 opened this issue Sep 9, 2023 · 3 comments

Comments

@Enchufa2
Copy link

Enchufa2 commented Sep 9, 2023

Describe the bug
When setup-r-dependencies has to compile everything (e.g. for r-devel), pak seems to hit some resource limitation, and the runner is shutdown with exit code 143.

To Reproduce
Here's the failing build: https://github.com/r-quantities/units/actions/runs/6089790695/job/16523324348

Further explanation is given in the raw logs:

2023-09-09T11:00:44.1688629Z ℹ Building vdiffr 1.0.6
2023-09-09T11:02:12.8425126Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
2023-09-09T11:02:12.8441147Z ##[error]Process completed with exit code 143.
2023-09-09T11:02:13.2338146Z Cleaning up orphan processes

Expected behavior
The runner should not be shutdown.

Additional context
About this error code: actions/runner-images#6680

@Enchufa2 Enchufa2 added the bug an unexpected problem or unintended behavior label Sep 9, 2023
Enchufa2 added a commit to r-quantities/workflows that referenced this issue Sep 9, 2023
@gaborcsardi
Copy link
Member

This is probably a bug in vdiffr or gcc: r-lib/vdiffr#137
A workaround is to use an earlier version of vdiffr, like this: rstudio/vetiver-r@b5f0692

There isn't much we can do about this here.

@gaborcsardi gaborcsardi removed the bug an unexpected problem or unintended behavior label Sep 9, 2023
@trevorld
Copy link

An alternative workaround to using an earlier version of {vdiffr} that just worked for me would be to "switch" the gcc version from 11.4.0 to 12.3.0 using something like:

      - name: Upgrade gcc to compile vdiffr without error
        if: matrix.config.r == 'devel'
        run: |
            sudo apt-get install -y g++-12 gcc-12 # probably already installed
            sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-12 60
            sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-12 60

@github-actions
Copy link

github-actions bot commented Oct 7, 2023

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants