175
81%

Ran 07 Aug 2018 03:16AM UTC

Jobs 4

Files 65

Run time 27s

Badge

Embed ▾

pending completion

Build # 175

Build Type

push

travis-ci

Committed by

rtobar

Commit Message

Communicating logical graph key all the way down

Until now we had no way to connect a particular drop to its node in the
original Logical Graph (if it came from there, that is). We are needing
this nowadays because of the work Vitaliy is doing to "close the loop"
between measuring the execution of a physical graph and putting that
information back into the Logical Graph.

Until now the way oids are constructed by the translator means that one
could use these to extract the Logical Graph key, but it was cumbersome
and required internal knowledge of the formula used to create oids, plus
some parsing. The new way is much easier to use and more explicit about
what this piece of information represents.

The keys from the logical graph nodes need to be passed down from: a)
the logical graph into the physical graph, b) the physical graph into
each drop instance, and c) each drop instance and the events they
generate. This commit includes these three communications, but making
sure drops and events still work for drops that were not created from a
Logical Graph.

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

Run Details

6447 of 9334 relevant lines covered (69.07%)

2.75 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	175.1	07 Aug 2018 03:16AM UTC	69.0	Travis Job 175.1
2	175.2	07 Aug 2018 03:16AM UTC	68.61	Travis Job 175.2
3	175.3	07 Aug 2018 03:16AM UTC	68.68	Travis Job 175.3
4	175.4	07 Aug 2018 03:16AM UTC	69.02	Travis Job 175.4

Source Files on build 175

Detailed source file information is not available for this build.

ICRAR / daliuge / 175
81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 175

ICRAR / daliuge / 175 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 175

ICRAR / daliuge / 175
81%

README BADGES
x