Skip to content

CI: Add self hosted riscv64 runners#3190

Open
yuzibo wants to merge 1 commit intonextest-rs:mainfrom
yuzibo:test-riscv64-runner
Open

CI: Add self hosted riscv64 runners#3190
yuzibo wants to merge 1 commit intonextest-rs:mainfrom
yuzibo:test-riscv64-runner

Conversation

@yuzibo
Copy link

@yuzibo yuzibo commented Mar 19, 2026

This is one attempt to add self hosted riscv64 runner for CI job.

@yuzibo yuzibo force-pushed the test-riscv64-runner branch from c5644c1 to fa8f5b1 Compare March 19, 2026 07:25
@yuzibo yuzibo marked this pull request as draft March 19, 2026 07:26
@codecov
Copy link

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.35%. Comparing base (54cb257) to head (713a496).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3190      +/-   ##
==========================================
+ Coverage   85.32%   85.35%   +0.03%     
==========================================
  Files         158      159       +1     
  Lines       46888    47018     +130     
==========================================
+ Hits        40005    40131     +126     
- Misses       6883     6887       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@yuzibo
Copy link
Author

yuzibo commented Mar 19, 2026

Okay. I have to admit we have one test case that failed due to timeout I think. see here.

Or could you help me to confirm this also?

sunshowers added a commit that referenced this pull request Mar 19, 2026
Fixes an issue identified in #3190 -- this shows up as 00:00:01 elapsed, breaking the snapshot.
@sunshowers
Copy link
Member

@yuzibo good catch -- fixed in #3197.

sunshowers added a commit that referenced this pull request Mar 19, 2026
Fixes an issue identified in
#3190 -- this shows up as
00:00:01 elapsed, breaking the snapshot.
@yuzibo yuzibo force-pushed the test-riscv64-runner branch from fa8f5b1 to dfabdec Compare March 20, 2026 02:43
@sunshowers
Copy link
Member

@yuzibo do I have to do anything on my end to configure self-hosted runners? (Probably, right?)

@yuzibo
Copy link
Author

yuzibo commented Mar 20, 2026

@yuzibo do I have to do anything on my end to configure self-hosted runners? (Probably, right?)

I think no? If zizmor job has been added to nextest's CI workflow as Trevor Gross suggests.

And I am waiting for the result from the job :) I forgot to push the latest code to my branch.

Once done, I need the token from your side to register the riscv64 runner. Please to read this link then Then we can agree on a time to pass the token which will be expired in one hour.

@yuzibo
Copy link
Author

yuzibo commented Mar 20, 2026

hmm, test failed again.

let me to check it again

@yuzibo yuzibo force-pushed the test-riscv64-runner branch from dfabdec to 713a496 Compare March 20, 2026 10:22
@yuzibo yuzibo marked this pull request as ready for review March 20, 2026 10:37
runs-on: ${{ matrix.os }}
# NOTE: self-hosted riscv64 runners are experimental and may be flaky.
# Do not block CI on failures from this platform for now at inital stages of support.
continue-on-error: ${{ contains(matrix.os, 'self-hosted') }}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can keep it running for a while then to decide if enable it nor not

@sunshowers
Copy link
Member

Once done, I need the token from your side to register the riscv64 runner. Please to read this link then Then we can agree on a time to pass the token which will be expired in one hour.

Thanks. I've read the documentation. What time of day works best for you? I can do 17:00-21:00 Pacific Sunday March 22 or Monday March 23 (00:00-04:00 Monday March 23/Tuesday March 24 in UTC). After that my next availability is the same time, Sunday March 29.

@yuzibo
Copy link
Author

yuzibo commented Mar 21, 2026

Thanks. I've read the documentation. What time of day works best for you? I can do 17:00-21:00 Pacific Sunday March 22 or Monday March 23 (00:00-04:00 Monday March 23/Tuesday March 24 in UTC). After that my next availability is the same time, Sunday March 29.

All times sound good to me. So we can do it at 00:00-04:00 Monday March 23 in UTC. Is it okay for you? Or let's sync this on zulipchat IM again.

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.

2 participants