ci: build riscv64 wheel on RISE runner via uv#2
Conversation
Today's scheduled run built the wheel but the release job failed: it targeted the self-hosted F3 board ([self-hosted, linux, riscv64]) and could not acquire a runner. The board is shared by several fork builds and contends weekly. Move build to the RISE ubuntu-24.04-riscv runner with uv-provisioned Python (astral-sh/setup-uv), matching the working httptools build - RISE runners have no bare python3, and uv installs a managed riscv64 Python independent of runner-image churn. Move the release job to ubuntu-latest (it only downloads the artifact and creates a release, no riscv64 needed) and correct the now-inaccurate Built on note. Signed-off-by: Bruno Verachten <gounthar@gmail.com>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The scheduled
Build riscv64 wheelrun #25982742827 built the wheel fine but the release job failed: it targets the self-hosted F3 board ([self-hosted, linux, riscv64]) and was never acquired (cancelled after multiple attempts). That board is shared by several fork builds and contends weekly.This fork is not redundant:
openai-harmonyships no riscv64 wheels on PyPI (0.0.8 has arm64/aarch64/x86_64 etc., not riscv64) and upstream openai/harmony#98 ("Add riscv64") is still open. This build is the only riscv64 wheel source, so the fix is reliability, not removal.Change (mirrors the watchfiles / safetensors / orjson fixes)
build->runs-on: ubuntu-24.04-riscv(RISE native runner) +astral-sh/setup-uv+uv venv --python 3.12, matching the sibling httptools build that runs there green. maturin/venv flow otherwise unchanged (--manifest-path Cargo.tomlpreserved).release->runs-on: ubuntu-latest(only downloads the artifact + creates a release; no riscv64 needed). This is the job that failed today.Workflow is
active, so no re-enable needed. The next scheduled run validates end-to-end.