Test coverage report numbers are inconsistant with Ruby MRI

[gogainda]

Taken from here
Ruby MRI 2.7.0

--------------------------------------------------------------------------------

1710 tests, 1821 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications

100% passed

--------------------------------------------------------------------------------

1352.88 tests/s, 1440.70 assertions/s

Coverage report generated for Unit Tests to /home/travis/build/namusyaka/gammo/.coverage. 3104 / 3204 LOC (96.88%) covered.

Truffleruby head

1710 tests, 1821 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications

100% passed

--------------------------------------------------------------------------------

70.29 tests/s, 74.86 assertions/s

Coverage report generated for Unit Tests to /home/travis/build/namusyaka/gammo/.coverage. 2983 / 3179 LOC (93.83%) covered.

Line coverage (93.83%) is below the expected minimum coverage (95.00%).

SimpleCov failed with exit 2

rake aborted!

[eregon]

Thanks for the report.
It would probably be useful to compare the SimpleCov HTML reports to find what are the differences.

[gogainda]

Happens again for omniauth/omniauth#1008

[bjfish]

@gogainda A fix for coverage was added here which should would to get enough coverage for omniauth. I see (96.9%) covered locally.
e68afb3

[gogainda]

@bjfish thanks for fixing it , I will double check the results

[gogainda]

https://travis-ci.org/github/omniauth/omniauth/builds/729730701 tests are passing and coverage is correct