This allows fully automated code coverage testing, which is
basically awesome. To allow the methods and solvers and stuff
which run as _apt to write to our build directory, we need to
adjust the permissions a bit, but otherwise it's OK.
Gbp-Dch: ignore
- sudo apt-get -qq -y -t xenial install cmake ninja-build
- sudo ./prepare-release travis-ci
before_script:
- sudo apt-get -qq -y -t xenial install cmake ninja-build
- sudo ./prepare-release travis-ci
before_script:
- - ( mkdir build && cd build && cmake -G Ninja .. )
+ - ( mkdir build && cd build && cmake -DCMAKE_BUILD_TYPE=Coverage -G Ninja .. )
- ninja -C build
script:
- CTEST_OUTPUT_ON_FAILURE=1 ninja -C build test
- DESTDIR=$PWD/rootdir chronic ninja -C build install
- ./test/integration/run-tests -qq
- sudo adduser --force-badname --system --home /nonexistent --no-create-home --quiet _apt || true
- ninja -C build
script:
- CTEST_OUTPUT_ON_FAILURE=1 ninja -C build test
- DESTDIR=$PWD/rootdir chronic ninja -C build install
- ./test/integration/run-tests -qq
- sudo adduser --force-badname --system --home /nonexistent --no-create-home --quiet _apt || true
+ - sudo chmod go+x /home/travis
+ - sudo chmod -R go+rwX /home/travis/build
- sudo ./test/integration/run-tests -qq
- sudo ./test/integration/run-tests -qq
+after_success:
+ - cd build
+ - gcov -r $(find -name '*.gcno')
+ - bash <(curl -s https://codecov.io/bash)