criu/scripts/travis/travis-after_success

#!/bin/sh
set -x -e

# We only need to run the below for gcov-enabled builds
test -z "$GCOV" && exit 0

sudo apt-get install -qq -y lcov
gem install coveralls-lcov
sudo lcov --directory ../.. --capture --output-file coverage.info --ignore-errors graph
coveralls-lcov coverage.info
CI: move travis' after_success to a script It is easier to handle it this way Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-10-11 18:46:57 -07:00			`#!/bin/sh`
			`set -x -e`

CI: move GCOV flag to travis.yml Move GCOV to travis environment, so now we can change it easily on a per-build basis. Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-10-11 18:46:59 -07:00			`# We only need to run the below for gcov-enabled builds`
Makefile, travis: unify checking GCOV env var Setting GCOV environment variable is used for doing profiling (gcov). Unfortunately, it is checked in two different ways: 1. In top Makefile and scripts/travis, it is checked against "1". 2. In other places, it's checked to be set to a non-empty value. So, giving various values to GCOV will lead to different results. Let's unify the approaches used. Apparently, among all the code the easiest (and not too strict) way is to check for non-empty value (this also leads to the smallest possible patch size). Note that in Python, evaluating an empty string in a binary context (such as after an "if" statement) equals to False. Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-10-20 20:04:47 -07:00			`test -z "$GCOV" && exit 0`
CI: move GCOV flag to travis.yml Move GCOV to travis environment, so now we can change it easily on a per-build basis. Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-10-11 18:46:59 -07:00
CI: move travis' after_success to a script It is easier to handle it this way Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-10-11 18:46:57 -07:00			`sudo apt-get install -qq -y lcov`
			`gem install coveralls-lcov`
travis: fix collecting code coverage The problem is in the chroot test: geninfo: ERROR: /home/travis/build/xemul/criu/test/zdtm/static/chroot.dir.test/home/travis/build/xemul/criu/images/timer.gcno: could not open file We can just ignore these errors. travis-ci: success for travis: fix collecting code coverage Signed-off-by: Andrei Vagin <avagin@virtuozzo.com> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2017-02-02 11:19:00 +03:00			`sudo lcov --directory ../.. --capture --output-file coverage.info --ignore-errors graph`
CI: move travis' after_success to a script It is easier to handle it this way Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-10-11 18:46:57 -07:00			`coveralls-lcov coverage.info`