diff options
author | Alex Bennée <alex.bennee@linaro.org> | 2023-04-03 14:49:10 +0100 |
---|---|---|
committer | Alex Bennée <alex.bennee@linaro.org> | 2023-04-04 15:16:29 +0100 |
commit | 899c3fc2dc66f6fd152322504eb321da4020ecd1 (patch) | |
tree | d72c1a25d20e519c898956532e7b7f78852ccaeb /MAINTAINERS | |
parent | 51a6dc9d394098e8f4141fad869a1ee9585f54f8 (diff) |
scripts/coverage: initial coverage comparison script
This is a very rough and ready first pass at comparing gcovr's json
output between two different runs. At the moment it will give you a
file level diff between two runs but hopefully it wont be too hard to
extend to give better insight.
After generating the coverage results you run with something like:
./scripts/coverage/compare_gcov_json.py \
-a ./builds/gcov.config1/coverage.json \
-b ./builds/gcov.config2/coverage.json
My hope is we can use this to remove some redundancy from testing as
well as evaluate if new tests are actually providing additional
coverage or just burning our precious CI time.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Cc: Kautuk Consul <kconsul@linux.vnet.ibm.com>
Acked-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20230403134920.2132362-2-alex.bennee@linaro.org>
Diffstat (limited to 'MAINTAINERS')
-rw-r--r-- | MAINTAINERS | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/MAINTAINERS b/MAINTAINERS index ef45b5e71e..9e1a60ea24 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3908,3 +3908,8 @@ Performance Tools and Tests M: Ahmed Karaman <ahmedkhaledkaraman@gmail.com> S: Maintained F: scripts/performance/ + +Code Coverage Tools +M: Alex Bennée <alex.bennee@linaro.org> +S: Odd Fixes +F: scripts/coverage/ |