Github Action failed with out of memory error

[mickael-danjoux]

I would like to deploy a project with Github Action.
I can't use SSH copy file because I can't add all IP addresses in white list on my server.

So I use a Linux self-hosted runner to try.

When I test my connexion with the server in the goal of testing a simple action, it works perfectly.

name: Hello World
on: [push]

jobs:
  one:
    name: Hello
    runs-on: self-hosted
    steps:
      - run: echo "hello world"

But when I want to use some actions like checkout, it works with 'ubuntu-20.04' but not with a self hosted runner on my server.

name: Deployment to production

on:
  push:
    branches:
      - master
     
jobs:
  auto-pull:
    name: Build and deploy
    runs-on: self-hosted
    steps:
    - uses: actions/checkout@v2

In Github Repo settings, my runner is green with 'Idle'

I do not see any errors in logs of the runner on the server.
I juste see 'Job Build and deploy completed with result: Failed' in the CLI just after the workflow start.
In Github, the workflow failed with 'Out of memory' error after a few time.

So I would like to find a solution to use Self-hosted runner or another method to solve the problem of the SSH access to deploy my project.
Thanks in advance

[TingluoHuang]

@mickd3 what is in the runner diag log? you can find them under the _diag folder of the runner root directory.

[mickael-danjoux]

@TingluoHuang I see a lot of information that seems like normal. I see the action checkout with ' "condition": "success()" '.
At the end of the file there is a lot of logs with 'info' status, but I don't see any warning or error information. This is a big file and I don't know what I have to search but at first glance it seems like normal

[hross]

Hello! We would like to help you solve this issue, but since this is not an engineering issue with the runner code (which is what we use this repo for) I'd like to redirect this discussion. If you are having issues with actions you need troubleshooting help with you can:

• File a Support Ticket if you are a paying customer.
• Post in the Community Forums for Actions if you are on a free account.

In both cases we have dedicated support people who monitor those areas and can help diagnose issues, as well as channels where you can securely share your logs/data/etc which won't be transmitted publicly over the internet (since this repo is open source these issues are freely available to anyone).

Apologies for the hassle of rewriting some of your problem and redirecting but I think it will make it easier and more secure for you to get help. Thanks!

[figadore]

Since this issue is high on the Google results for this error, I hope it's ok to offer my workaround here. I was able to get a memory-intensive job to run by adding swap space (e.g. using this GitHub Action)

[ericdallo]

@figadore thanks! how much do you recommend for the swap for a windows runner?
I'm currently having OOM errors for graalvm builds only for windows, linux and mac works good