title: CodeClimate coverage analysis is wrong on Travis CI
body: <p>I am having a problem with codeclimate-test-reporter and Travis CI on my new project. The coverage analysis on Travis CI is completely different from what it is locally. Specifically, the LOC locally is 56 (which is accurate), but it's listed as 10,333 when I build the project on Travis CI.</p>
  
  <h2>Code and Output</h2>
  
  <p><strong>Local Output</strong> (56 / 56 LOC)</p>
  
  <pre><code>Finished in 0.0749 seconds (files took 0.60563 seconds to load)
  7 examples, 0 failures
  
  Coverage report generated for RSpec to /Users/lee/GitHub/rescuetime/coverage. 
  56 / 56 LOC (100.0%) covered.
  Coverage = 100.0%. Sending report to https://codeclimate.com for branch 
  data-analytics-api... done.
  </code></pre>
  
  <p><strong>Travis CI Output</strong> (4954 / 10333 LOC?!)</p>
  
  <pre><code>Coverage report generated for RSpec to /home/travis/build/leesharma/rescuetime/coverage. 
  4954 / 10333 LOC (47.94%) covered.
  Coverage = 47.94%. Sending report to https://codeclimate.com for branch 
  data-analytics-api... done.
  </code></pre>
  
  <p><a href="https://github.com/leesharma/rescuetime/blob/master/spec/spec_helper.rb" rel="nofollow"><strong>spec_helper.rb</strong></a> (bits relating to codeclimate-test-reporter)</p>
  
  <pre><code>require 'codeclimate-test-reporter'
  require 'simplecov'
  SimpleCov.formatter = SimpleCov::Formatter::MultiFormatter[
      SimpleCov::Formatter::HTMLFormatter,
      CodeClimate::TestReporter::Formatter
  ]
  SimpleCov.start
  ...
  
  VCR.configure do |config|
    ...
    config.ignore_hosts 'codeclimate.com'
  end
  </code></pre>
  
  <p><a href="https://github.com/leesharma/rescuetime" rel="nofollow"><strong>Full project source code</strong></a></p>
  
  <h2>What I've tried</h2>
  
  <p>I've confirmed that the code is exactly the same, and these results are the same for each ruby tested (both locally and on Travis CI, >=1.9.3 MRI). I tried limiting it to just one ruby version for Travis, but the results are the same. I've tried searching for similar issues, but so far, I've only found an open/unanswered GitHub issue on their repo. </p>
  
  <p>Honestly, I'm not even sure what to try next for debugging this since I can't reproduce it locally. Any idea what to try next?</p>