Closed mattbement closed 9 months ago
Can you try an MPI barrier on transfer_comm
right before you free that communicator at the end of main
? I want to make sure there's not some kind of barrier missing here.
Can you try an MPI barrier on
transfer_comm
right before you free that communicator at the end ofmain
? I want to make sure there's not some kind of barrier missing here.
OK maybe that's not it. I'll cross reference this with out unit tests.
@Rombur @masterleinad Matt's problem has sources only on rank 0 and targets only on rank 1. I don't think we have a good test for this one. Matt's test is pretty simple and should be easy to add to the unit tests.
At Stuart's suggestion, if I uncomment the intialization of coord0 and coord1 to 0 length views, things seem to work fine. Note that the nearest neighbor operator worked fine without having to initialize these to 0 length.
@Rombur @masterleinad Should we support uninitialized views and assume them to be size 0?
This would have failed with DBC in place (and I think that should be enabled in Debug mode by default).
In general, I would consider any use of uninitialized Kokkos::View
objects a user error.
This would have failed with DBC in place (and I think that should be enabled in Debug mode by default). In general, I would consider any use of uninitialized
Kokkos::View
objects a user error.
Would you please post a reference to the assertion that you expect would fail?
Would you please post a reference to the assertion that you expect would fail?
DataTransferKit
is going to be archived.
For the simple test program below, I get an error in MPI_Waitall. If I switch to the nearest neighbor operator, everything works as expected.