Refactor CI workflows for improved release and sync testing#67
Refactor CI workflows for improved release and sync testing#67pablomendezroyo merged 2 commits intomainfrom
Conversation
…leae.yml, sync-test.yml, and sync.yml for improved release and sync testing processes
✅ SYNC TEST REPORT - PASSEDThis 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. The self-hosted runner is pre-loaded with synced (or near-synced) execution client volumes, enabling fast sync and attestation tests with any client combination. Consensus clients use checkpoint sync, so no pre-synced volume is required. Sync Test: Verifies that both execution and consensus clients reach a synced state. This test ensures the staker configuration is valid and clients can synchronize with the network. 📦 Clients Used
🔖 Version TrackingExecution Client Versions
Consensus Client Versions
⏱️ Timing MeasurementsEnvironment Setup
Test Execution
Total Duration: 3m25s 🔴 Container Error Logs
DAppNodePackage-brain.web3signer-hoodi.dnp.dappnode.eth: DAppNodePackage-validator.teku-hoodi.dnp.dappnode.eth: |
This update removes outdated CI workflows and introduces new workflows for release and sync testing, enhancing the overall efficiency and organization of the CI process.