Closed jcortejoso closed 1 year ago
Coverage from tests in ./e2e_test/...
for ./consensus/istanbul/...
at commit 2c709330ac6d3d69cfad1896876c6ab336b00c08
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.2% 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.4% 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
Attention: 48 lines
in your changes are missing coverage. Please review.
Comparison is base (
0ed594e
) 55.10% compared to head (8617a40
) 55.14%. Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description
Dockerfile.arm64
supporting ARM builds. This image is different from the existing Dockerfile because:linux-headers
andlinux-headers-arm64
) with different name for both architectures. It may be possible to add some logic to the Dockerfile to be able to share the same for linux/amd64 and linux/arm64 platforms, but really I don't see a lot of value on investing time there tbh.Other changes
Dockerfile.arm64
expected for Android buildsmycelo
, skip the transfer ownsership of governance for local and loadTest mycelo templatesTested
Images generated: https://github.com/celo-org/celo-blockchain/actions/runs/6315913589/workflow
Pending
Update the reference to the composite actions when https://github.com/celo-org/reusable-workflows/pull/72 is merged