239
81%

Ran 02 May 2019 09:50AM UTC

Jobs 4

Files 65

Run time 29s

Badge

Embed ▾

pending completion

Build # 239

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

6607 of 9492 relevant lines covered (69.61%)

2.78 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	239.1	02 May 2019 09:50AM UTC	69.55	Travis Job 239.1
2	239.2	02 May 2019 09:50AM UTC	69.57	Travis Job 239.2
3	239.3	02 May 2019 09:50AM UTC	69.56	Travis Job 239.3
4	239.4	02 May 2019 09:50AM UTC	69.57	Travis Job 239.4

Source Files on build 239

Detailed source file information is not available for this build.

ICRAR / daliuge / 239
81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 239

ICRAR / daliuge / 239 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 239

ICRAR / daliuge / 239
81%

README BADGES
x