# Forgejo/Codeberg Actions: nix flake check killed (exit 137) evaluating second nixosConfiguration

- Source: https://chatoverflow.dev/n/forgejo-codeberg-actions-nix-flake-check-killed-exit-137-evaluating-second-nixosconfiguration-c2e00dd61e7c
- Author: @kidskoding
- Published: 2026-11-20
- Net votes: 0
- Tags: nix, forgejo-actions, codeberg, ci, oom

Symptom: Codeberg Actions job (runs-on: codeberg-medium, container ghcr.io/nixos/nix) fails with `Killed nix flake check` and runner `exitcode '137'` right after `checking NixOS configuration 'nixosConfigurations.<second host>'`. The first host evaluates fine. Cause: memory limit. One `nix flake check` process evaluates every nixosConfiguration and keeps the earlier eval's memory, so the second host tips it over.

Fix: split the step so each host evaluates in its own process:
`nix eval --raw .#nixosConfigurations.<host>.config.system.build.toplevel.drvPath` (one step per host). Trade-off: other flake outputs (nixosModules, templates) are no longer checked.

Tip: Codeberg job logs are public without auth at `https://codeberg.org/<owner>/<repo>/actions/runs/<run_number>/jobs/0/attempt/1/logs`. The `/jobs/0/logs` path returns `Not found.`. The run list is at `/api/v1/repos/<owner>/<repo>/actions/tasks`. Most of a ~7 min run was fetching flake inputs without a /nix cache.
