ci: add integration tests for write-program-buffer#2
Open
sparten11740 wants to merge 7 commits into
Open
Conversation
Three prebuilt SBF binaries for the integration tests: small (544 B), big (4,680 B, delta 4,136 for the SIMD-0431 clamp scenario), and huge (10,482,400 B unpacked, gzipped to 10 KB) for the near-max scenario. Built once with cargo-build-sbf --arch v3 and deploy-verified against a local all-features validator; README documents regeneration.
…cenario The integration workflow boots a local test validator per matrix cell (solana 3.1.14 and 4.1.2 via setup-all) and runs the action against it. The fresh path asserts the buffer contents match the artifact, the authority stays with the deployer, and no resize or transfer happens.
…ction Consumer repos and this repo's own integration tests share the same need: boot a local test validator and wait for health. The action exposes rpc-url and ledger-dir outputs; the test workflow now consumes it instead of a scenario-local script.
Each scenario becomes its own matrix cell alongside the solana version, giving per-scenario check reporting and full isolation. A shared output contract on the prepare scripts (keypair, deployer, program-id, buffer-authority, pre-len) keeps the action invocation scenario-agnostic.
Deploys the small fixture, grows the artifact by 4,136 bytes, and asserts the programdata account grew by exactly 10,240 bytes - the minimum extend size the clamp must produce. Also verifies the buffer contents match the grown artifact.
Deploys the small fixture and hands the action a third keypair as buffer-authority-address. Asserts the buffer's on-chain authority equals that address and no longer equals the deployer - the handoff the Squads flow depends on.
Extends a deployed program to within 5,315 bytes of the 10 MiB cap, then runs the action with the padded 10,482,400-byte artifact. The action must extend by exactly the remaining headroom - the SIMD-0431 carve-out where the 10 KiB minimum does not apply - landing the account at precisely 10,485,760 bytes. The setup extend retries across block boundaries since the loader rejects two extends of the same program in one block.
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.
No description provided.