tests: use the (now) already-installed gcovr binary
What the developer wrote
Authored by Jon Griffiths
tests: use the (now) already-installed gcovr binary
What changed, and why it matters
This is a tiny CI (continuous integration) maintenance change. It removes a redundant pip install command for a code-coverage tool called gcovr, because that tool is now pre-installed in the test environment. There is no change to the actual library code, cryptography, or anything users interact with.
No security action needed; routine CI hygiene change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies .gitlab-ci.yml only, removing ‘pip install gcovr’ from the test_cmake job. The subsequent gcovr invocation remains unchanged. This is a build/test pipeline cleanup with no functional code changes.
Changed components
.gitlab-ci.ymlInspect captured patch +0 / −1
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 340e0d3..1a471ed 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -82,7 +82,6 @@ test_cmake:
- cd build-cmake
- ctest --output-on-failure
- cd -
- - pip install gcovr
- gcovr --xml-pretty --exclude-unreachable-branches --print-summary -o coverage.xml --root ${CI_PROJECT_DIR}
coverage: /^\s*lines:\s*\d+.\d+\%/
artifacts:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.