diff options
| author | Alex Bennée | 2022-11-17 18:25:30 +0100 |
|---|---|---|
| committer | Alex Bennée | 2022-11-22 10:52:23 +0100 |
| commit | 5544d33d4b3683861315c73eb956492ed8891ce8 (patch) | |
| tree | 3d0a0a101f8bdf5d42fae8f856aaf34238ba6587 | |
| parent | tests/avocado: skip aarch64 cloud TCG tests in CI (diff) | |
| download | qemu-5544d33d4b3683861315c73eb956492ed8891ce8.tar.gz qemu-5544d33d4b3683861315c73eb956492ed8891ce8.tar.xz qemu-5544d33d4b3683861315c73eb956492ed8891ce8.zip | |
gitlab: integrate coverage report
This should hopefully give is nice coverage information about what our
tests (or at least the subset we are running) have hit. Ideally we
would want a way to trigger coverage on tests likely to be affected by
the current commit.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20221117172532.538149-12-alex.bennee@linaro.org>
| -rw-r--r-- | .gitlab-ci.d/buildtest.yml | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml index 7173749c52..d21b4a1fd4 100644 --- a/.gitlab-ci.d/buildtest.yml +++ b/.gitlab-ci.d/buildtest.yml @@ -494,7 +494,17 @@ check-gprof-gcov: IMAGE: ubuntu2004 MAKE_CHECK_ARGS: check after_script: - - ${CI_PROJECT_DIR}/scripts/ci/coverage-summary.sh + - cd build + - gcovr --xml-pretty --exclude-unreachable-branches --print-summary + -o coverage.xml --root ${CI_PROJECT_DIR} . *.p + coverage: /^\s*lines:\s*\d+.\d+\%/ + artifacts: + name: ${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}-${CI_COMMIT_SHA} + expire_in: 2 days + reports: + coverage_report: + coverage_format: cobertura + path: build/coverage.xml build-oss-fuzz: extends: .native_build_job_template |