fix: try re-enable buildjet for RPC checks

[LesnyRumcajs]

Summary of changes

Changes introduced in this pull request:

• in the past it was failing but now it seems fine. Not sure what happened, but this should resolve issues around Lotus OOM in the RPC checks. If not, we can always revert.

Reference issue to close (if applicable)

Closes #6029

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Summary by CodeRabbit

• Chores
  • Updated CI/CD infrastructure configuration to use an alternate build environment for testing workflows.

[coderabbitai]

Walkthrough

The rpc-parity GitHub Actions workflow runner environment was updated from ubuntu-24.04 to buildjet-8vcpu-ubuntu-2204. This changes the underlying OS image and compute resources used to execute the workflow steps.

Changes

Cohort / File(s)	Summary
CI workflow runner update .github/workflows/rpc-parity.yml	Modified job runner from ubuntu-24.04 to buildjet-8vcpu-ubuntu-2204 for the rpc-parity job

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• Move RPC checks to buildjet #6029: Directly addresses the same objective of switching the RPC parity workflow runner to BuildJet to prevent Lotus OOM issues.

Possibly related PRs

• chore: use buildjet ubuntu in calibnet rpc check ci #5878: Directly related—implements the identical runner change from ubuntu-24.04 to buildjet-8vcpu-ubuntu-2204 for the same workflow file.
• chore: remove disk usage tricks for buildjet #5892: Related—modifies the same RPC parity workflow file for BuildJet adaptation by removing disk-relocation steps.
• Revert to ubuntu-24.04 from buildjet in rpc parity workflow #5902: Related—modifies the same workflow file but reverts the runner back to ubuntu-24.04 with additional Docker volumes relocation configuration, indicating potential conflict resolution.

Suggested reviewers

• akaladarshi
• hanabi1224
• elmattic

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "fix: try re-enable buildjet for RPC checks" directly and accurately describes the main change in the changeset, which modifies the .github/workflows/rpc-parity.yml workflow to switch the job runner from ubuntu-24.04 to buildjet-8vcpu-ubuntu-2204. The title is clear, specific, and uses descriptive language (mentioning both the action "re-enable buildjet" and the scope "for RPC checks") rather than vague terms. A teammate scanning the repository history would clearly understand that this PR changes the infrastructure used for RPC checks, and the use of "try" reflects the PR's intent to be reversible if needed.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch try--buildjet-rpc

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/rpc-parity.yml (2)

9-9: Add inline documentation explaining the BuildJet migration.

The PR description mentions this resolves Lotus OOM issues, but this context is not captured in code. Add a comment above the runs-on field to document the rationale, making future maintainers aware of the decision and its trade-offs.

Apply this diff to add context:

  rpc-parity:
    name: RPC parity tests
+   # Using BuildJet (third-party runner) to mitigate Lotus OOM issues
+   # observed with ubuntu-24.04. If OOM issues persist, consider reverting
+   # to ubuntu-24.04 or investigating heap limits.
    runs-on: buildjet-8vcpu-ubuntu-2204

---

9-9: Add actionlint configuration to suppress custom runner warning.

BuildJet is confirmed as a legitimate third-party GitHub Actions runner service (Y Combinator startup). The workflow is already properly configured to mitigate OOM issues by relocating Docker volumes to /mnt (60GB+ available space).

However, actionlint will flag buildjet-8vcpu-ubuntu-2204 as an unknown runner label. Add .github/actionlint.yml to suppress this:

self-hosted-runner:
  labels:
    - buildjet-8vcpu-ubuntu-2204

Optionally, add an inline comment in the workflow explaining the OOM mitigation rationale for future reference.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9f7fe8 and b758b4d.

📒 Files selected for processing (1)

• .github/workflows/rpc-parity.yml (1 hunks)

🧰 Additional context used

🪛 actionlint (1.7.8)

.github/workflows/rpc-parity.yml

9-9: label "buildjet-8vcpu-ubuntu-2204" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Build forest binaries on Linux AMD64
• GitHub Check: tests-release
• GitHub Check: tests