Skip to content

ci: run the runtime-sapling-params tests filtered in one job - #2

Merged
j0ntz merged 1 commit into
EdgeApp:jon/runtime-sapling-paramsfrom
zingolabs:ci/3112-filtered-sapling-params
Nov 5, 2026
Merged

j0ntz merged 1 commit into
EdgeApp:jon/runtime-sapling-paramsfrom
zingolabs:ci/3112-filtered-sapling-params

Conversation

@Oscar-Pepper

Copy link
Copy Markdown
  • fixes CI fails
  • adds specific test for loading sapling params from a set directory
  • only runs runtime-sapling-params specific tests instead of whole suite

🤖 Generated with Claude Code

The feature gates one module, wallet::sapling_params, which owns the
directory and every test gated on the feature. Running zingolib's whole
lib suite under it re-ran hundreds of tests the feature cannot reach,
across four shards fed a parameter artifact that upload-artifact never
produced, since it skips the hidden cache directory. One job now checks
the default build to fill the cache and runs that module's tests plus
the mock-chain Sapling spend with the feature on. test.yaml returns to
dev's shape. A new test loads and parses the prover from a directory the
consumer populates, the path an app takes after downloading the files.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@j0ntz
j0ntz merged commit c11bea4 into EdgeApp:jon/runtime-sapling-params Nov 5, 2026
21 of 29 checks passed
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