Skip to content

ci: build riscv64 wheel on RISE runner via uv#2

Merged
gounthar merged 1 commit into
mainfrom
fix/riscv64-build-reliability
May 17, 2026
Merged

ci: build riscv64 wheel on RISE runner via uv#2
gounthar merged 1 commit into
mainfrom
fix/riscv64-build-reliability

Conversation

@gounthar
Copy link
Copy Markdown
Owner

The scheduled Build riscv64 wheel run #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-harmony ships 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.toml preserved).
  • release -> runs-on: ubuntu-latest (only downloads the artifact + creates a release; no riscv64 needed). This is the job that failed today.
  • Corrected the now-inaccurate "Built on: BananaPi F3" release note to "RISE riscv64 runner".

Workflow is active, so no re-enable needed. The next scheduled run validates end-to-end.

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>
@gemini-code-assist
Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 17, 2026

Warning

Rate limit exceeded

@gounthar has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minute and 45 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9f2de9a4-735f-48cb-b5c5-81031f56fdf5

📥 Commits

Reviewing files that changed from the base of the PR and between 6541fdf and 50032c4.

📒 Files selected for processing (1)
  • .github/workflows/build-riscv64.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/riscv64-build-reliability

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gounthar gounthar merged commit 001c615 into main May 17, 2026
24 checks passed
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