ActRuner hungs up VPS server #13535

New Issue

GiteaMirror · 2025-11-02T10:45:21-06:00

GiteaMirror commented

2025-11-02 10:45:21 -06:00

Originally created by @stuzer05 on GitHub (Sep 26, 2024).

Description

So the problem is I run this actions script

name: test backend

on: [push]

jobs:
  test:
    runs-on: ubuntu-latest
    env:
        DB_CONNECTION: mysql
        DB_DATABASE: laravel
        DB_USERNAME: root
        DB_PASSWORD: root

    services:
        mysql:
            image: mysql:latest
            ports:
                - 3306/tcp
            env:
                MYSQL_DATABASE: laravel
                MYSQL_ROOT_PASSWORD: root
            options: --health-cmd="mysqladmin ping" --health-interval=10s --health-timeout=5s --health-retries=3

    steps:
      - uses: actions/checkout@v2
      - uses: shivammathur/setup-php@v2
        with:
            php-version: 8.3

      #- run: sudo /etc/init.d/mysql start

      #- run: cp .env.ci .env
      - run: composer install
      - run: php artisan key:generate
      - run: php artisan test

It creates tmp containers but then server stops respongind, ssh laggs, docker ps taking too long to print etc. I have to reboot the server to later gind out this error in gitea actions logs

What could be the broblem?

Gitea Version

1.23.0+dev-526-g3269b04d61

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

PostgreSQL

Originally created by @stuzer05 on GitHub (Sep 26, 2024). ### Description So the problem is I run this actions script ```yaml name: test backend on: [push] jobs: test: runs-on: ubuntu-latest env: DB_CONNECTION: mysql DB_DATABASE: laravel DB_USERNAME: root DB_PASSWORD: root services: mysql: image: mysql:latest ports: - 3306/tcp env: MYSQL_DATABASE: laravel MYSQL_ROOT_PASSWORD: root options: --health-cmd="mysqladmin ping" --health-interval=10s --health-timeout=5s --health-retries=3 steps: - uses: actions/checkout@v2 - uses: shivammathur/setup-php@v2 with: php-version: 8.3 #- run: sudo /etc/init.d/mysql start #- run: cp .env.ci .env - run: composer install - run: php artisan key:generate - run: php artisan test ``` It creates tmp containers but then server stops respongind, ssh laggs, docker ps taking too long to print etc. I have to reboot the server to later gind out this error in gitea actions logs ![image](https://github.com/user-attachments/assets/7a71660f-7644-47c3-8e50-0218a2537751) What could be the broblem? ### Gitea Version 1.23.0+dev-526-g3269b04d61 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? docker ### Database PostgreSQL

GiteaMirror added the topic/gitea-actions issue/needs-feedback labels 2025-11-02 10:45:21 -06:00

GiteaMirror closed this issue

2025-11-02 10:45:22 -06:00

GiteaMirror commented

2025-11-02 10:45:22 -06:00

@wxiaoguang commented on GitHub (Sep 29, 2024):

For > 99% cases: you triggered an OOM crash.

When a program (eg: an action job) consumes too much memory, all programs on the server including SSH would stop working, just like what you described.

@wxiaoguang commented on GitHub (Sep 29, 2024): For > 99% cases: you triggered an OOM crash. When a program (eg: an action job) consumes too much memory, all programs on the server including SSH would stop working, just like what you described.

GiteaMirror commented

2025-11-02 10:45:22 -06:00

@stuzer05 commented on GitHub (Sep 29, 2024):

For > 99% cases: you triggered an OOM crash.

When a program (eg: an action job) consumes too much memory, all programs on the server including SSH would stop working, just like what you described.

You suggest I need a server with more RAM?

@stuzer05 commented on GitHub (Sep 29, 2024): > For > 99% cases: you triggered an OOM crash. > > When a program (eg: an action job) consumes too much memory, all programs on the server including SSH would stop working, just like what you described. You suggest I need a server with more RAM?

GiteaMirror commented

2025-11-02 10:45:23 -06:00

@wxiaoguang commented on GitHub (Sep 29, 2024):

You suggest I need a server with more RAM?

If it is really caused by OOM: yes

You could try to monitor the memory / CPU usage by some tools like dstat, to figure out the real bottleneck.

@wxiaoguang commented on GitHub (Sep 29, 2024): > You suggest I need a server with more RAM? If it is really caused by OOM: yes You could try to monitor the memory / CPU usage by some tools like `dstat`, to figure out the real bottleneck.

GiteaMirror commented

2025-11-02 10:45:23 -06:00

@stuzer05 commented on GitHub (Sep 29, 2024):

Thank you, will look into it

@stuzer05 commented on GitHub (Sep 29, 2024): Thank you, will look into it

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13535