Refactor CI workflows for improved build and testing#54
Refactor CI workflows for improved build and testing#54pablomendezroyo wants to merge 2 commits intomainfrom
Conversation
…yml for improved build and 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: 2m33s 🔴 Container Error Logs
DAppNodePackage-validator.teku-hoodi.dnp.dappnode.eth: |
Refactor the continuous integration workflows by removing the outdated main.yml and introducing release.yml and sync-test.yml to enhance the build and testing processes.