ci: run the forge tests as a normal user in the CI gate job #693

Open
opened 2026-10-03 16:55:53 +00:00 by hexajon · 0 comments
Owner

What

The CI gate job runs in the golang:1.27-trixie container as root. The
workflow sets no user, and the Go build cache mounts at
/root/.cache/go-build. Forgejo and Gitea refuse to start as root, and the
harness neither switches user nor turns off that refusal. So when the forge
tests run in CI, every forge test fails there.

What to build

  • The CI gate job runs go test as a normal user.
  • The Go cache mounts move to the home directory of that user.
  • That user can read and write the checkout and the caches.

Acceptance

  • The CI gate log shows that the forge tests ran as a non-root user against
    both forges, with no skipped forge test.
  • No CI step turns off the refusal of a forge to run as root.

Part of #674. #678 needs this.

## What The CI `gate` job runs in the `golang:1.27-trixie` container as root. The workflow sets no user, and the Go build cache mounts at `/root/.cache/go-build`. Forgejo and Gitea refuse to start as root, and the harness neither switches user nor turns off that refusal. So when the forge tests run in CI, every forge test fails there. ## What to build - The CI `gate` job runs `go test` as a normal user. - The Go cache mounts move to the home directory of that user. - That user can read and write the checkout and the caches. ## Acceptance - The CI `gate` log shows that the forge tests ran as a non-root user against both forges, with no skipped forge test. - No CI step turns off the refusal of a forge to run as root. Part of #674. #678 needs this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
sixfold-space/madtea#693
No description provided.