Inconsistent results when run inside Flowhub

[bergie]

Here is how Flowhub triggers fbp-spec (with a pre-existing runtime connection): https://github.com/noflo/noflo-ui/blob/master/components/RunTests.coffee

However, the results are inconsistent when shown in the UI:

This doesn't conform to what I see in the runtime console where the states appear to be what was expected:

undefined 'Portal c-base space station is L4 RESISTANCE'
undefined 'Portal c-base space station is L8 RESISTANCE'
undefined 'Portal c-base space station is L8 ALIENS'
undefined 'Portal c-base space station (NEUTRAL) is L8 and has disco'
undefined 'Portal c-base space station is L8 RESISTANCE'
undefined 'Portal c-base space station has special disco mods'
undefined 'Portal c-base space station has special disco mods’

When the same tests are run inside Node.js Mocha runner, they all pass: https://travis-ci.org/c-base/ingress-table/builds/77374093#L446

[bergie]

Similar thing appears to happen when running multiple suites, with the latter suite receiving the output of the first one:

These also pass with Node.js Mocha: https://travis-ci.org/noflo/noflo-hackrf/builds/77363801#L221

[jonnor]

Probably something in runner.coffee, in which case it should also manifest when running tests with fbp-spec executable.

[jonnor]

Could also be that if the runtime sends messages from an old network, we don't properly ignore them.
Possibly related to that we (currently) never send a network:stop message.

[jonnor]

Think I solved the Ingress Table issue in c-base/ingress-table@c524173