ci: give the release link swap on GitHub runners #136

Merged

jcoffey-dev merged 1 commits from ci/release-link-swap into main

2026-09-30 20:45:24 +00:00

jcoffey-dev commented

2026-09-30 20:37:44 +00:00

Owner

The v2026.9.30 tag build (GitHub run 36764295827) lost its arm64 publish job at the final link of inbuxa: rustc was SIGKILLed after 38 min with ResourceExhausted … cannot allocate memory. The release profile is fat LTO with one codegen unit, and the 16 GB ubuntu-24.04-arm runner ran out. amd64 got through on the same size of runner. Because of that, index, ghcr, release, binaries, github-release and the announcement were all skipped. Production is unaffected: the nodes run the amd64 image, which was published.

Each publish job now adds a 16 GB swap file before the build. buildx's container has no memory limit of its own, so the linker can use the host's swap.
The step logs free -g and df -h /, so the next tag build shows the headroom.

This can't be tested on a PR, because publish only runs on tags. It first runs on the next tag (2026.9.30.1, planned right after this lands). A re-run of the v2026.9.30 run would still use that tag's old workflow.

No new strings.

The v2026.9.30 tag build ([GitHub run 36764295827](https://github.com/inbuxa/inbuxa-server/actions/runs/36764295827)) lost its arm64 publish job at the final link of `inbuxa`: rustc was SIGKILLed after 38 min with `ResourceExhausted … cannot allocate memory`. The release profile is fat LTO with one codegen unit, and the 16 GB `ubuntu-24.04-arm` runner ran out. amd64 got through on the same size of runner. Because of that, `index`, `ghcr`, `release`, `binaries`, `github-release` and the announcement were all skipped. Production is unaffected: the nodes run the amd64 image, which was published. - Each `publish` job now adds a 16 GB swap file before the build. buildx's container has no memory limit of its own, so the linker can use the host's swap. - The step logs `free -g` and `df -h /`, so the next tag build shows the headroom. This can't be tested on a PR, because publish only runs on tags. It first runs on the next tag (2026.9.30.1, planned right after this lands). A re-run of the v2026.9.30 run would still use that tag's old workflow. No new strings.

jcoffey-dev added 1 commit 2026-09-30 20:37:44 +00:00

ci: give the release link swap on GitHub runners

ci / fork-checks (pull_request) Skipped

Details

ci / build (pull_request) Skipped

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 7m25s

Details

ce2742fc80

The v2026.9.30 tag build's arm64 publish job was killed linking the
inbuxa binary (fat LTO, one codegen unit): cannot allocate memory on the
16 GB ubuntu-24.04-arm runner. index, ghcr, release, binaries and
announce were skipped. amd64 got through on the same size of runner.

Each publish job now adds a 16 GB swap file before the build; buildx's
container has no memory limit of its own, so the linker can use it.

jcoffey-dev merged commit 78c9490b1e into main

2026-09-30 20:45:24 +00:00

jcoffey-dev deleted branch ci/release-link-swap

2026-09-30 20:45:24 +00:00

jcoffey-dev referenced this pull request

2026-09-30 20:45:47 +00:00

Release 2026.9.30.1 #137

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#136