search

jrl-umi3218 / jrl-travis

Travis build scripts
Other
7 stars 10 forks source link

Possible Coveralls error #11

Closed bchretien closed 10 years ago

bchretien commented 10 years ago

I noticed that the coveralls data is apparently no longer forwarded to coveralls.io, for instance for RobOptim's Ipopt plugin: https://coveralls.io/r/roboptim/roboptim-core-plugin-ipopt

This is worth investigating.

bchretien commented 10 years ago

This could be due to https://github.com/jrl-umi3218/jrl-travis/commit/1e4aedf12e8546838a8e8c9ba564a4ef8a17ba80.

bchretien commented 10 years ago

The investigation lead me to some errors in cpp-coveralls (https://github.com/eddyxu/cpp-coveralls/pull/39 and https://github.com/eddyxu/cpp-coveralls/pull/40). Now files seem to be detected, at least locally (e.g. https://coveralls.io/builds/701776), so we'll be able to see if things are back to normal on Travis.

bchretien commented 10 years ago

If we want more control, another solution could also be to use lcov-based solutions instead (cf. https://github.com/ddemidov/vexcl/pull/106).

thomas-moulard commented 10 years ago

Looks good, that would be a nice, improvement :) Thanks for looking into this!

bchretien commented 10 years ago

Moving to lcov/coveralls-lcov works (https://github.com/jrl-umi3218/jrl-travis/commit/04636a7113e5e485ba1553dc131c6af600279082), but now we need to solve coveralls.io-related errors (cf. https://github.com/lemurheavy/coveralls-public/issues/263).

Current result: https://coveralls.io/builds/704774

bchretien commented 10 years ago

Things seem to be working now: https://coveralls.io/builds/706099 Only relevant files are considered, i.e. system files are ignored, and the user can also choose to remove test programs.