linux ci: contents: write for nightly release publish#90
Merged
Conversation
…a week The GitHub-hosted nightly-linux has failed every day for 8+ days, across many commits predating any recent work — all exit 143 (SIGTERM/OOM). Firefox is too big for the 16GB standard runner without swap. Same fix that got the Windows lane past its OOM wall: 24G swapfile (ubuntu leg; fedora runs in a container where swapon isn't available) + cap mach at -j2 so concurrent heavy TUs don't exhaust RAM. The sovereign builder (32c/128GB) stays at full parallelism.
With the OOM fix, the ubuntu build finally SUCCEEDED for the first time — and immediately exposed a latent packaging bug: the tarball step tarred a dist/bearbrowser/ dir that only 'mach package' creates, but the workflow only ran 'mach build' (which leaves dist/bin). Never surfaced before because the build always OOM'd first. Now run 'mach package' (proven on the sovereign Linux builder) and ship its real dist/bearbrowser-*.tar.xz (with omni.ja). Also mark the fedora leg continue-on-error: it builds in a container where swapon isn't available (so no OOM headroom) and hits a mirror-recipe cfg-copy quirk. Ubuntu is the primary Linux artifact and stays blocking.
The ubuntu leg now BUILDS + PACKAGES + makes the AppImage successfully (the swap+mach-package fixes worked) — it failed only at the final 'Publish nightly release' step: the default GITHUB_TOKEN is read-only, so 'gh release upload --clobber' 403'd (hidden by 2>/dev/null) and the fallback 'gh release create' errored on the nightly-<date> tag a sibling lane had already created. Same one-line permissions fix already on nightly-dmg + nightly-windows. This is the last step before the first green Linux nightly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ubuntu leg now builds + packages + AppImages successfully — the swap + mach-package fixes worked. It failed only at the final
Publish nightly releasestep because the workflow lackedpermissions: contents: write(unlike nightly-dmg/nightly-windows): the read-only token madegh release upload --clobber403 (hidden by2>/dev/null), and the fallbackgh release createerrored on thenightly-<date>tag a sibling lane already made. One-line fix, identical to the other two lanes. Last step before the first-ever green Linux nightly.