ICRAR / daliuge / 122

68%

master: 80%

push

travis-ci

Moving drop triggering down

Most probably due to historical reasons drop triggering was happening
not at the very end of a session deployment step, but actually further
important drop customization was happening after drop triggering, like
creation and linking of drop proxies and zeromq event publishers. We
have seen some intermittent failures in some unit test runs, and this
situation could probably explain them (but because they appear *very*
infrequently we cannot say for sure).

However, this change is small, doesn't seem to break the unit tests
(fingers crossed!), so in it goes.

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

1 of 1 new or added line in 1 file covered. (100.0%)

5927 of 8753 relevant lines covered (67.71%)

2.7 hits per line