Closed jcortejoso closed 11 months ago
Coverage from tests in ./e2e_test/...
for ./consensus/istanbul/...
at commit f6cfb3a089ff2d89b458140be02fd08f3caf79a9
coverage: 63.0% of statements in consensus/istanbul coverage: 40.0% of statements in consensus/istanbul/announce coverage: 54.6% of statements in consensus/istanbul/backend coverage: 0.0% of statements in consensus/istanbul/backend/backendtest coverage: 24.3% of statements in consensus/istanbul/backend/internal/replica coverage: 61.1% of statements in consensus/istanbul/core coverage: 45.0% of statements in consensus/istanbul/db coverage: 0.0% of statements in consensus/istanbul/proxy coverage: 64.2% of statements in consensus/istanbul/uptime coverage: 51.8% of statements in consensus/istanbul/validator coverage: 79.2% of statements in consensus/istanbul/validator/random
Test failures: |
---|
TestEthClient: ethclient
|
TestEthClient/TestTxInBlockInterrupted: ethclient
|
This test report was produced by the test-summary action. Made with ❤️ in Cambridge. |
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
a59dd19
) 55.09% compared to head (f8dc509
) 55.05%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description
Refactor the GitHub workflow for celo-blockchain release images:
release/1.8.x
that it's the current patternus-west1-docker.pkg.dev/devopsre/celo-blockchain-public
registry as they are duplicated.Tested manually. The
tagged
releases (i.e. with tag v1.8.0) could not be tested because the security contraints require that the tag created follow the pattern vx.y.z, and I did not want to create a fake release for testing.