Skip to content

Commit

Permalink
Merge pull request #236 from drmingdrmer/rm-stale-log-id-test
Browse files Browse the repository at this point in the history
Test: disable stale_last_log_id(), very easy to get timeout
  • Loading branch information
drmingdrmer authored Mar 5, 2022
2 parents 3e92156 + 57842f1 commit 88a5a60
Showing 1 changed file with 5 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,12 @@ use crate::fixtures::RaftRouter;

/// Ensures the stale value of ReplicationCore.last_log_id won't affect replication.
/// If `ReplicationCore.last_log_id` is used, the end position of log for loading may underflow the start.
///
/// TODO(xp): `max_applied_log_to_keep` to be 0 makes it very easy to enter snapshot replication and it will keeps
/// replicating every log by snapshot and get timeout.
/// Thus it is disabled until we find another way to test it.
#[tokio::test(flavor = "multi_thread", worker_threads = 8)]
#[ignore]
async fn stale_last_log_id() -> Result<()> {
let (_log_guard, ut_span) = init_ut!();

Expand Down

0 comments on commit 88a5a60

Please sign in to comment.