[PATCH 0/5] Add Binman code-coverage test to CI
Simon Glass
sjg at chromium.org
Thu Jun 20 15:19:32 CEST 2024
Binman has 100% code coverage to ensure that future changes and
refactors do not break existing entry types. This is a critical feature,
given that it is relied on to produce images for all sorts of different
SoCs and vendors.
With the NXP additions the 'binman test -T' step was missed, so the
Binman coverage test is currently failing.
This series provides a means to close the testing gap. It cannot be
applied until the tests are added, which should happen before -next is
applied to -master
Simon Glass (5):
Dockerfile: Add python3-coverage
Dockerfile: Add python3-pycryptodome
buildman: Support building within a Python venv
u_boot_pylib: Use correct coverage tool within venv
CI: Run code-coverage test for Binman
.gitlab-ci.yml | 4 +-
tools/buildman/bsettings.py | 3 ++
tools/buildman/test.py | 83 +++++++++++++++++++++++++++++++++
tools/buildman/toolchain.py | 31 ++++++++++--
tools/docker/Dockerfile | 2 +
tools/u_boot_pylib/test_util.py | 11 +++--
6 files changed, 126 insertions(+), 8 deletions(-)
--
2.34.1
More information about the U-Boot
mailing list