• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

chrisly-bear / cscc-recommender / 102 / 1
32%
master: 32%

Build:
DEFAULT BRANCH: master
Ran 01 Jun 2018 01:55PM UTC
Files 19
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

01 Jun 2018 01:37PM UTC coverage: 31.181% (-0.06%) from 31.244%
102.1

push

travis-ci

chrisly-bear
Fixed a bug. We must not use a global field for overall context terms when indexing to Lucene. If we use a global field we only store the last term of the overall context. What happens is that, in the for loop, we keep changing the previously added term by calling overallContextField.setStringValue because we always call the setStringValue on the same object. What we end up with is a Lucene Document where the same field (our overallContextField) is added several times, but the field always has the same value (namely the value that was set in the last run through the for loop).

338 of 1084 relevant lines covered (31.18%)

7.49 hits per line

Source Files on job 102.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 33
  • Travis Job 102.1
  • a37dd099 on github
  • Prev Job for on master (#101.1)
  • Next Job for on master (#104.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc