Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi PLCT team,
I'd like to request access to an RVLab machine to run native riscv64 verification for my open-source project.
About me / the project
I'm an OSPP 2026 (开源之夏) student contributor working on SkillHub (iflytek/skillhub), an open-source Agent Skill platform by iFLYTEK. My project adds an Agent Skill authoring and validation platform (upstream PR: iflytek/skillhub#886). The stack is architecture-neutral by design (pure JVM bytecode + POSIX tools), and I've already verified it under QEMU riscv64 emulation — I'd now like to reproduce the verification on real riscv64 hardware and record the evidence honestly, as the project's RISC-V compatibility commitment requires.
What I plan to run
Thanks for maintaining the lab!