1
62%
master: 62%

Ran 13 Nov 2018 03:09PM UTC

Files 15

Run time 1s

Badge

Embed ▾

Committed 13 Nov 2018 03:05PM UTC coverage: 28.041% (-0.4%) from 28.481%

Job # 134.1

Build Type

push

travis-ci

Committed by

jrdh

Commit Message

Properly define the index and finish signals

In the non-multiprocess indexer class we could implement an
index signal which gets the mongo doc and list of commands
each time a record is handled, however in the multiprocess
version we can't do this as we'd have to pass the mongo doc
and commands back through to the main process which would
then trigger the signal. This will be horrible from a
performance angle which is what we're shooting for with the
multiprocessing variant. Therefore, only the counts are sent
and no more information. This ensures that the index signal
receives the same parameters regardless of which backend
indexer class is in use.

Run Details

136 of 485 relevant lines covered (28.04%)

0.28 hits per line

NaturalHistoryMuseum / eevee / 134 / 1
62%
master: 62%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 134.1

NaturalHistoryMuseum / eevee / 134 / 1 62% master: 62%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 134.1

NaturalHistoryMuseum / eevee / 134 / 1
62%
master: 62%

README BADGES
x