Summary
Follow-up to #7477 (comment).
.github/workflows/external-rpc-checks.yml currently only runs on a daily schedule and a bare workflow_dispatch, always against ghcr.io/chainsafe/forest:edge-fat (hardcoded in scripts/tests/external-rpc-checks/docker-compose.yaml). There is no way to point it at a suspicious branch, nor to opt a PR into the check.
Two related capabilities are wanted:
-
Dispatch against a specific build. workflow_dispatch should accept an image (and ideally build one locally from the selected ref), so a branch can be exercised against the external dataset before merging. rpc-parity.yml already does the image-input
-
Label-driven runs on PRs, mirroring the existing RPC / Snapshot labels.
Completion Criteria
Additional Links & Resources
Summary
Follow-up to #7477 (comment).
.github/workflows/external-rpc-checks.ymlcurrently only runs on a dailyscheduleand a bareworkflow_dispatch, always againstghcr.io/chainsafe/forest:edge-fat(hardcoded inscripts/tests/external-rpc-checks/docker-compose.yaml). There is no way to point it at a suspicious branch, nor to opt a PR into the check.Two related capabilities are wanted:
Dispatch against a specific build.
workflow_dispatchshould accept an image (and ideally build one locally from the selected ref), so a branch can be exercised against the external dataset before merging.rpc-parity.ymlalready does the image-inputLabel-driven runs on PRs, mirroring the existing RPC / Snapshot labels.
Completion Criteria
Additional Links & Resources