Skip to content

CI: tolerate a single-device DEVICE_RANGE (fix intermittent a5 job crash)#933

Merged
ChaoWao merged 1 commit into
hw-native-sys:mainfrom
ChaoWao:fix/ci-device-range
May 31, 2026
Merged

CI: tolerate a single-device DEVICE_RANGE (fix intermittent a5 job crash)#933
ChaoWao merged 1 commit into
hw-native-sys:mainfrom
ChaoWao:fix/ci-device-range

Conversation

@ChaoWao
Copy link
Copy Markdown
Collaborator

@ChaoWao ChaoWao commented May 31, 2026

Summary

The a5 hardware jobs (ut-a5, st-onboard-a5) and the a2a3 resource-spec step parse ${DEVICE_RANGE} with s, e = ...split('-'). When the runner's DEVICE_RANGE is a single id (no hyphen), the unpack raises ValueError: not enough values to unpack (expected 2, got 1) and the job fails before any test runs — an intermittent failure we hit repeatedly across recent PRs.

Fix: parse into a list and take first/last (s, e = p[0], p[-1]), so both "4" (→ s=e=4) and "0-7" (→ s=0, e=7) work. Applied to all 5 split sites.

Testing

  • Logic verified locally: "4"4, "0-7"0,1,…,7, "0"0
  • ci.yml YAML parses; pre-commit clean

The a5 jobs (and the a2a3 resource-spec step) split ${DEVICE_RANGE} on '-' and
unpack into (s, e). When the runner's DEVICE_RANGE is a single id (no hyphen)
the unpack raises `ValueError: not enough values to unpack (expected 2, got 1)`
and the job dies before any test runs — an intermittent ut-a5 / st-onboard-a5
failure. Parse into a list and take first/last instead, so "4" -> s=e=4 and
"0-7" -> s=0,e=7 both work. Fixes all 5 split sites.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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 31, 2026

Warning

Review limit reached

@ChaoWao, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 4 minutes and 39 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 92c38206-79f0-4c91-ac3c-dfad1362b5a8

📥 Commits

Reviewing files that changed from the base of the PR and between 39c0445 and c37a717.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

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.

@ChaoWao ChaoWao merged commit d8c1fff into hw-native-sys:main May 31, 2026
30 of 31 checks passed
@ChaoWao ChaoWao deleted the fix/ci-device-range branch May 31, 2026 06:55
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