Skip to content

ci: align staking test workflows with TropiBot retries#88

Open
3alpha wants to merge 1 commit into
mainfrom
ci/tropibot-dispatch-metadata
Open

ci: align staking test workflows with TropiBot retries#88
3alpha wants to merge 1 commit into
mainfrom
ci/tropibot-dispatch-metadata

Conversation

@3alpha

@3alpha 3alpha commented Jul 13, 2026

Copy link
Copy Markdown
Member

Summary

  • Forward an immutable `head_sha` to the reusable staking workflows so TropiBot retries always retest the exact PR head.
  • Keep the existing `ipfs_hash` opt-in (skip build when supplied) for manual reruns of the PR head.
  • Preserve the reth execution client default and the consensus-client choice for sync / attestation tests.

Details

`sync-test.yml`

  • Forwards `head_sha: ${{ github.event.client_payload.head_sha || github.event.pull_request.head.sha || github.sha }}`.
  • Existing `pull_request`, `workflow_dispatch`, and `repository_dispatch: [tropibot-sync-test]` triggers preserved.
  • `ipfs_hash` is optional and falls back to building the PR head when empty.

`attestation-test.yml`

  • Forwards `head_sha: ${{ github.event.client_payload.head_sha || github.sha }}` (command/manual-only triggers).
  • Supports `workflow_dispatch` and `repository_dispatch: [tropibot-attestation-test]`.
  • `ipfs_hash` is optional and falls back to building the PR head when empty.

Dependency

Depends on the corresponding `dappnode/workflows` reusable-workflow update being merged first.

@tropibot

tropibot Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

✅ TropiBot report: SYNC TEST REPORT - PASSED

This CI runs on a real DAppNode using the same RPC calls a user would make to configure a staker setup: execution client, consensus client, web3signer, MEV-boost, and relays.

📦 Package Under Test

📦 Clients Used

Component DNP Name
Execution hoodi-reth.dnp.dappnode.eth
Consensus nimbus-hoodi.dnp.dappnode.eth
Web3Signer web3signer-hoodi.dnp.dappnode.eth
MEV Boost mev-boost-hoodi.dnp.dappnode.eth
Network hoodi

🔖 Version Tracking

Client Before After
Execution reth/v2.0.0-eb4c15e/x86_64-unknown-linux-gnu reth/v2.3.0-9384bc5/x86_64-unknown-linux-gnu
Consensus n/a Nimbus/v25.9.2-9839f1-stateofus

⏱️ Timing

Operation Duration Status
SetStakerConfig 1m 43s
PackageInstall 1m 4s
WaitForSync 0.0s

Total Duration: 3m 17s


📋 View full CI logs

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.

1 participant