Chris Hall

Results 34 comments of Chris Hall

Strange, from your travis log I see 2 interesting sections The first time coveralls only analyses one files, the second time it analyses 'a lot'. https://travis-ci.org/GlPortal/RadixEngine/builds/212253813#L506 ``` [100%] Built target...

Attempted reproduction steps roughly following https://github.com/GlPortal/RadixEngine/blob/master/COMPILE.md (I tried to use a `build` dir at first but it didn't seem to add anything, so tried without) ``` $ sudo pacman -S...

`make test` seems to run the tests for RadixEngine ``` [chris@niflheim RadixEngine]$ git remote -vv origin https://github.com/GlPortal/RadixEngine.git (fetch) origin https://github.com/GlPortal/RadixEngine.git (push) [chris@niflheim RadixEngine]$ make test Running tests... Test project /home/chris/devel/RadixEngine...

So in RadixEngine it looks like: + `make tests` will build the tests + `make test` and `ctest` are equialent - either one will run the tests ``` [chris@niflheim RadixEngine]$...

As a side effect of investigating this I noticed an issue in that you have a public .coveralls.yml (only needed for private travis, not needed for open source.) I created...

Okay, I now have coveralls running outside the docker container and I'm able to reproduce the 0% coveralls report on my clone.

tests and output: Running: - ctest inside docker ONCE - cpp-coveralls outside docker ONCE gives 0% coverage Log: https://api.travis-ci.org/v3/job/401344880/log.txt ``` before_install: - docker pull glportal/whale-gcc:coverall - pip install --user cpp-coveralls...

Confirmed that the single build isn't producing the profile data ``` - docker pull glportal/whale-gcc:coverall - pip install --user cpp-coveralls script: - docker run -it --rm -w /data -v $(pwd):/data...

So poking around in CMakeFiles/ with grep looking for 'coverage' we get single run of everything ``` before_install: - docker pull glportal/whale-gcc:coverall - pip install --user cpp-coveralls script: - docker...

So at the very least, your cmake config is buggy, as these two commands produce different outputs: `cmake -DCOVERAGE:BOOL=ON ./&& make && make tests && ctest` `cmake -DCOVERAGE:BOOL=ON && cmake...