Repository navigation
Add a CI workflow - #2
Merged
Merged
Conversation
Three jobs, in rkwhisper's style: no third-party actions beyond checkout and upload-artifact, and rustup installed inline. The main job runs on arm64, so what it builds and tests is what the board runs. The NPU runtime is resolved by dlopen, so nothing in CI needs it. It adds clippy with warnings denied, which the workspace is already clean under. A second job tests the frontend on x86_64. The design claims it needs no hardware and builds anywhere, and that job is what keeps the claim true. A third builds release binaries and uploads them. One wrinkle worth naming. .cargo/config.toml points the aarch64 target at a cross linker, which is right when building for the board from an x86_64 host. On an arm64 runner that triple is the host, so the workflow overrides the linker to cc. Verified locally that the environment variable does take precedence over the checked-in config. Every command the workflow runs was run on stable first, including the release build, so CI is not the first place they are tried. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NQQRfiJcmrzXmnwKkJfAug
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.
Three jobs, in rkwhisper's style: no third-party actions beyond checkout and upload-artifact, and rustup installed inline.
The main job runs on arm64, so what it builds and tests is what the board runs. The NPU runtime is resolved by dlopen, so nothing in CI needs it. It adds clippy with warnings denied, which the workspace is already clean under.
A second job tests the frontend on x86_64. The design claims it needs no hardware and builds anywhere, and that job is what keeps the claim true.
A third builds release binaries and uploads them.
One wrinkle worth naming. .cargo/config.toml points the aarch64 target at a cross linker, which is right when building for the board from an x86_64 host. On an arm64 runner that triple is the host, so the workflow overrides the linker to cc. Verified locally that the environment variable does take precedence over the checked-in config.
Every command the workflow runs was run on stable first, including the release build, so CI is not the first place they are tried.
Claude-Session: https://claude.ai/code/session_01NQQRfiJcmrzXmnwKkJfAug