ci: rebuild inside cloned repo for devnet verify#74
Merged
Conversation
solana-verify verify-from-repo always re-clones the repo into a fresh temp directory; with --skip-build it expects the .so to already exist in that clone, which it never does (build-verified writes target/ in the workflow workspace, not the clone). The result was: Skipping local build and writing verify data on chain Uploading the program verification params to the Solana blockchain... Error: No such file or directory (os error 2) Set skip-build: 'false' so solana-verify performs its own Docker build inside the cloned repo before uploading the verification PDA. Adds a few minutes to the devnet release but makes the step actually work.
Compute Unit Report
Generated: 2026-04-30 |
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
1 participant
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.
Summary
skip-build: 'false'for the devnetverify-buildstep sosolana-verifyperforms its own Docker build inside the freshly cloned repo before uploading the verification PDA.Root Cause
solana-verify verify-from-repoalways re-clones the target repo into/tmp/solana-verify/<uuid>/.... With--skip-buildthe upload step expects the.soto already exist in that clone, but ourBuild verified programstep writes artifacts to the workflow workspace (/home/runner/work/...), not the clone. The upload then failed with:Letting solana-verify do its own Docker build inside the cloned repo costs a few extra minutes but makes the verification PDA upload work.
Test Plan
Releaseworkflow againstdevnetfrom this branch.Verify build (devnet)succeeds and a verification PDA is written forDe1egAFMkMWZSN5rYXRj9CAdheBamobVNubTsi9avR44.Failing run for reference: https://github.com/solana-program/subscriptions/actions/runs/25182511963