Repository navigation
Conversation
…manual, nothing is published) A pull request that changes the file runs the probe only (no secret). The builds are started by hand: gh workflow run arm-build.yml -f ref=<ref> -f jobs=linux|windows|all. Only screenshots are uploaded. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…-emulated job The first Windows runs built both ARM64 exes and both crashed ~4 s in (WARP, first frame). The diagnose step starts the exe with a bigger stack (the ARM64 exes reserve 1 MiB, the x64 MinGW release 2 MiB) and prints Windows' crash report; the new job starts the released x64 build under Windows' emulation, to tell the runner's software renderer from our build. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…ly some of the time) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…enderer, and variants)
…s/design/warp-start-crash.md)
This branch has not been deployed
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
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.
A manual workflow that builds the SpaceCorps 2027 client natively on GitHub's free Arm runners (
ubuntu-24.04-arm,windows-11-arm) and starts it headless 8 times per build. It proves what the x86_64 release PC cannot (Linux ARM64 only runs under QEMU there; a Windows on Arm exe cannot run at all). Nothing is released or published, no binary is uploaded (artifacts of a public repository are public), only the screenshots the headless game writes.SOURCE_TOKEN, likemac-build.yml; the build log stays on the runner, only each error's message and place and the game's own start-up lines are printed.gh workflow run arm-build.yml -R SpaceCorps/play --ref arm-build-check -f ref=<SpaceCorps2027 ref> -f jobs=probe|linux|windows|x64|all.x64is a control: the released x64 zip (sha-checked) started 8 times onwindows-11-armand onwindows-latest.docs/design/warp-start-crash.md). On 2026-11-05 fromlane/052-arm(which has the game's guard against it): Linux 8 of 8, Windows gnullvm 8 of 8, msvc 8 of 8. Details in the note.Part of SpaceCorps/SpaceCorps2027#50 (
docs/design/arm-builds.md, section 4). Do not merge before the owner says so; it only needs to be onmainif the release job should start it.🤖 Generated with Claude Code