Bug in communication JSON output about vt HOT 8 OPEN

@cz4rs @pierrepebay

Here is a pointer to the incorrect JSON: https://github.com/DARMA-tasking/vt-tv/blob/master/tests/unit/lb_test_data/data.0.json

An entity with "home": 0, "id": 0, exists in the communications, but is not present in the tasks. This data was generated using lb_iter on 4 ranks, that should reproduce the bug. I think this bug is easy to reproduce (probably with multiple benchmarks).

from vt.

I believe that this code:

Is creating that entry, but it's not being output as a task because maybe it's zero work?

from vt.

@cz4rs additionally if this can help, when I encountered the bug I went through the data (the one @lifflander pointed to) for the 4 ranks by hand, and sketched this out:

It shows what is contained in the communications section of the json for each of the 4 ranks, and whether the endpoints of each communication are present in the tasks field for that rank or not (circled in green or red). It shows how object 0 doesn't exist in any of the ranks.

from vt.

@pierrepebay Please post JSON that is incorrect.

from vt.

@lifflander I will write unit test for this that reproduces.

from vt.

Output from lb_iter with downsized problem (running on two ranks), bare handlers are marked explicitly:
data.1.json
data.0.json

from vt.