3
70%
master: 81%

Ran 02 May 2019 09:32AM UTC

Files 65

Run time 2s

Badge

Embed ▾

Committed 02 May 2019 09:26AM UTC coverage: 69.553%. First build

Job # 238.3

Build Type

push

travis-ci

Committed by

rtobar

Commit Message

Fixing remote linking to streaming consumers

When adding streaming consumers to a data drop we were checking whether
the drop given as a parameter "looked" like a streaming consumer by
checking for the presence of some methods. However, when executed in the
context of a multi-nm graph deployment, the object given to this
function can be a drop proxy, therefore triggering a remote call to the
remote actual drop, which might or might not exist at that point in time
(drops are created independently in parallel in all NMs).

This particular scenario was never experienced before, mainly because
streaming consumers/inputs are so rare in our exercises, but also
because there was no unit test exercising this particular functionality.
Now there is.

The fact that we are removing these checks shouldn't be too worrying: we
don't have these kind of checks for other linkage operations
(addProducer, addConsumer, etc) and we have survived without them.

Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>

Run Details

6602 of 9492 relevant lines covered (69.55%)

0.7 hits per line

ICRAR / daliuge / 238 / 3
70%
master: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 238.3

ICRAR / daliuge / 238 / 3 70% master: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 238.3

ICRAR / daliuge / 238 / 3
70%
master: 81%

README BADGES
x