Add code coverage via coveralls

[caniszczyk]

Lets try this again.

https://coveralls.io/r/twitter/algebird

Signed-off-by: Chris Aniszczyk zx@twitter.com

[coveralls]

Changes Unknown when pulling dcbbc05 on add-coveralls into * on develop*.

[caniszczyk]

@johnynek any idea why this fails for me?

"[info] - should measure 0.8 similarity in 1024 bytes with < 0.05 error *** FAILED ***
[info] 0.0625 was not less than 0.05 (MinHasherTest.scala:35)"

[coveralls]

Changes Unknown when pulling f224b30 on add-coveralls into * on develop*.

[johnynek]

@caniszczyk noisey test. These are probabilistic data structures. Sometimes you get unlucky.

[johnynek]

@caniszczyk thanks for getting this started. Trying again. Would love scalding and summingbird here too.

[johnynek]

So, this is green, but I don't see the coveralls badge. @caniszczyk thoughts? @travisbrown?

[travisbrown]

Hi @johnynek, you'll need to add the badge to the README—something like this would work.

I'm using shields.io SVG badges there, and I'm explicitly stating that the badges should reflect the status of the develop branch, since for example Travis's badge by default reflects the latest build on any branch, which isn't generally what you want.

[sriramkrishnan]

@johnynek since you aren't running coverageReport, what does this actually end up publishing?

[sriramkrishnan]

Sorry, I mean coverageAggregate - https://github.com/scoverage/sbt-scoverage#multi-project-reports