Skip to content

ci(native-cpu): drop linux-arm64 runner from multiarch matrix - #577

Merged
michalharakal merged 1 commit into
developfrom
feature/native-cpu-drop-linux-arm
Apr 30, 2026
Merged

michalharakal merged 1 commit into
developfrom
feature/native-cpu-drop-linux-arm

Conversation

@michalharakal

Copy link
Copy Markdown
Contributor

Summary

Temporarily removes the ubuntu-24.04-arm runner from the native-cpu cross-arch CI matrix introduced in #574 — it's been failing on this repo. The other three hosts (linux-x86_64, macos-arm64, windows-x86_64) keep running.

Linux ARM64 consumers fall back to Panama priority-50 cleanly when no native lib resolves — same cascade path the rest of the cross-arch story relies on. Re-adding is a one-line uncomment once either the GitHub-hosted ARM runner stabilises or a self-hosted ARM64 runner is wired in.

Test plan

  • Workflow still triggers on the three remaining matrix entries
  • CI run on this PR is green for linux-x86_64 / macos-arm64 / windows-x86_64

🤖 Generated with Claude Code

The ubuntu-24.04-arm runner has been failing in the cross-arch CI
matrix added in #574. Removing it from the matrix temporarily so
the workflow stays green on the three working hosts (linux-x86_64,
macos-arm64, windows-x86_64) while the runner-side issue is sorted
out. Linux ARM64 consumers cleanly fall back to the priority-50
Panama Vector provider when no native lib resolves — same fall-
through path the rest of the cross-arch story uses.

Re-adding ARM Linux is one-line: uncomment the matrix entry once
either the GitHub-hosted runner stabilises or a self-hosted ARM64
runner is wired in.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@michalharakal
michalharakal merged commit 9dfb624 into develop Apr 30, 2026
9 checks passed
@michalharakal
michalharakal deleted the feature/native-cpu-drop-linux-arm branch April 30, 2026 05:48
@michalharakal michalharakal mentioned this pull request Apr 30, 2026
MacOS pushed a commit to MacOS/SKaiNET that referenced this pull request Jul 10, 2026
- gradle.properties: drop -SNAPSHOT; RELEASE_SIGNING_ENABLED stays
  true.
- CHANGELOG: add 0.22.0 section covering the native (FFM) CPU
  kernel provider rollout (5-PR staged delivery SKaiNET-developers#571–SKaiNET-developers#575) plus
  publishing/CI/docs polish (SKaiNET-developers#576, SKaiNET-developers#577, SKaiNET-developers#579). Native Q4_K matmul
  is 4.17–5.87× faster than Panama Vector at LLM-typical shapes;
  native FP32 SGEMM 1.55–1.77× faster; zero-copy MemSeg path saves
  +20% wall-clock at 4096². Closes M5 milestone metric.
- README: bump Quickstart coordinates to 0.22.0; rewrite "What's
  New" section around the native FFM provider.
- .github/workflows/publish.yml: split into matrix build-native
  + publish so the published JAR carries libskainet_kernels for
  linux-x86_64 + macos-arm64 + windows-x86_64. Downstream devs
  on any of those three arches get a working native path on tag
  push without manual side-loading. Linux ARM64 stays unsupported
  (Kotlin/Native host limitation tracked in SKaiNET-developers#577).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant