Merge branch 'tmp-coverage' into 'master'

updates in code coverage calculation

See merge request openconnect/ocserv!97

.gitlab-ci.yml

@@ -69,7 +69,7 @@ Build/Fedora:
   # ensure gcov scripts are writable
   - umask 000
   - git submodule update --init && autoreconf -fvi &&
-    ./configure --disable-maintainer-mode --without-docker-tests --with-werror --enable-code-coverage && make -j$(nproc) && make check -j$(nproc) COVERAGE=1
+    CFLAGS="-g -O0" ./configure --disable-maintainer-mode --without-docker-tests --with-werror --enable-code-coverage && make -j$(nproc) && make check -j$(nproc) COVERAGE=1
     && make files-update && make dist && make local-code-coverage-output
   tags:
   - shared

README.md

@@ -1,5 +1,5 @@
-[![Build status](https://gitlab.com/ocserv/ocserv/badges/master/build.svg)](https://gitlab.com/ocserv/ocserv/commits/master)
-[![coverage report](https://gitlab.com/ocserv/ocserv/badges/master/coverage.svg)](https://ocserv.gitlab.io/ocserv/coverage/)
+[![Build status](https://gitlab.com/openconnect/ocserv/badges/master/build.svg)](https://gitlab.com/openconnect/ocserv/commits/master)
+[![coverage report](https://gitlab.com/openconnect/ocserv/badges/master/coverage.svg)](https://openconnect.gitlab.io/ocserv/coverage/)
 
 # About
 
@@ -130,7 +130,7 @@ You may examine the output using:
 We utilize the gitlab-ci continuous integration system. It is used to test
 most of the Linux systems (see .gitlab-ci.yml),and is split in two phases,
 build image creation and compilation/test. The build image creation is done
-at the ocserv/build-images subproject and uploads the image at the gitlab.com
+at the openconnect/build-images subproject and uploads the image at the gitlab.com
 container registry. The compilation/test phase is on every commit to project.