Skip to content

Commit

Permalink
#249: location: fix expected node in case of eager updates
Browse files Browse the repository at this point in the history
  • Loading branch information
hobywan authored and lifflander committed Mar 10, 2019
1 parent b61c5c8 commit 240eda7
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions tests/unit/location/test_location.cc
Original file line number Diff line number Diff line change
Expand Up @@ -128,10 +128,9 @@ TEST_F(TestLocation, test_migration_entity) {

if (my_node > 1) {
vt::theLocMan()->virtual_loc->getLocation(entity, 0, [my_node](vt::NodeType node) {
// fmt::print("this node={}: node={}\n", my_node, node);
// If the 0 node isn't the good one, it's the expected one because it is also the cached one
// A routMsg has been send to the last know node (the 0) one which is guarenty to know the correct node)
EXPECT_EQ(0, node);
// Edit: the expected node can be either 0 (initial) or 1 (migrated)
// The protocol may actually eagerly update other nodes
EXPECT_TRUE(node == 0 or node == 1);
});
} else {
vt::theLocMan()->virtual_loc->getLocation(entity, 0, [my_node](vt::NodeType node) {
Expand Down

0 comments on commit 240eda7

Please sign in to comment.