Coveralls hasn't seen much attention, is believed to be inaccurate for many comparisons of coverage changes (potentially comparing prior coveralls run instead of prior master run), and can cause stalls in the build process: https://github.com/druid-io/druid/issues/3067This proposal is to disable coveralls for druid-io/druid
--
You received this message because you are subscribed to the Google Groups "Druid Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/fc01f08c-1414-4baa-b49f-4c67cb427b7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
If cobertura is the underlying problem, we could try giving jacoco a shot, it seems to be more actively maintained and also has better Java 8 support already.
On Tue, Jun 7, 2016 at 3:15 PM, Charles Allen <charle...@metamarkets.com> wrote:
Coveralls hasn't seen much attention, is believed to be inaccurate for many comparisons of coverage changes (potentially comparing prior coveralls run instead of prior master run), and can cause stalls in the build process: https://github.com/druid-io/druid/issues/3067This proposal is to disable coveralls for druid-io/druid
--
You received this message because you are subscribed to the Google Groups "Druid Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-development+unsubscribe@googlegroups.com.
To post to this group, send email to druid-development@googlegroups.com.