summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNasser Grainawi <nasser@codeaurora.org>2020-10-30 16:38:51 -0600
committerGerrit Code Review <noreply-gerritcodereview@google.com>2020-10-30 22:38:51 +0000
commit780733adf0d9f59155235f4e29a45e05e512ce86 (patch)
treef8d9f34a8cedea854a6608dd2d355961368e62cd
parent1f5ed1e2d0b1c1629bdfa888384aadf561bf2d6f (diff)
Update git submodules
* Update plugins/replication from branch 'stable-3.0' to 4604b01e43c3b4aee3d03cb84945b3238c150ede - Merge branch 'stable-2.16' into stable-3.0 * stable-2.16: ReplicationStorageIT: Wait for all pushes without order ReplicationTasksStorage: Add multi-primary unit tests Change-Id: I1d749621c189ee2e49f092ddc7558f83e508411f - ReplicationStorageIT: Wait for all pushes without order Some tests don't have a predefined order for which events will be replicated first. Using a timeout based on a single replication event is flawed when we don't know the expected order. Instead, use a timeout for the group of events and ignore the order. For two events replicating to a single remote with a single thread, we expect the complete replication to take twice as long. Two events replicating to two remotes will use one thread each and therefore not take any longer than the single remote case. Change-Id: Ieb21b7eee32105eab5b5a15a35159bb4a837e363 - Merge "ReplicationTasksStorage: Add multi-primary unit tests" into stable-2.16 - ReplicationTasksStorage: Add multi-primary unit tests These tests examine the replication scenarios under multi-primary setup making use of the api calls present in ReplicationTasksStorage class similarly as done in single primary setup. These tests ensure that the replication compatibility in multi-primary setup is not broken. Change-Id: I375b731829f3c0640d3a7a98635e1e5c526908ca
m---------plugins/replication0
1 files changed, 0 insertions, 0 deletions
diff --git a/plugins/replication b/plugins/replication
-Subproject 8650a78b2682c90247435cfd807f0d0bacc84f9
+Subproject 4604b01e43c3b4aee3d03cb84945b3238c150ed