You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing proposals being refreshed after the first proposal in the test due to a reasonNewLeaderOrConfigChange. This is likely due to #38343, although I'm not sure how.
Fixescockroachdb#38525.
The test was occasionally failing because the proposals map was being refreshed
due to a `reasonNewLeaderOrConfigChange`. This was caused by 1ff3556, which
replaced `submitProposalFn` with `proposalBuf.testing.submitProposalFilter`. The
new approach to mocking out this function doesn't prevent a Raft ready iteration
from being scheduled, so `handleRaftReady` was being called and noticing the
leadership change, resulting in the refresh.
I've stressed this for 200,000 iterations without a failure.
Release note: None
38532: storage: deflake TestReplicaRefreshPendingCommandsTicks r=tbg a=nvanbenschoten
Fixes#38525.
The test was occasionally failing because the proposals map was being refreshed
due to a `reasonNewLeaderOrConfigChange`. This was caused by 1ff3556, which
replaced `submitProposalFn` with `proposalBuf.testing.submitProposalFilter`. The
new approach to mocking out this function doesn't prevent a Raft ready iteration
from being scheduled, so `handleRaftReady` was being called and noticing the
leadership change, resulting in the refresh.
I've stressed this for 200,000 iterations without a failure.
Co-authored-by: Nathan VanBenschoten <[email protected]>
The following tests appear to have failed on master (testrace): TestReplicaRefreshPendingCommandsTicks
You may want to check for open issues.
#1364461:
Please assign, take a look and update the issue accordingly.
The text was updated successfully, but these errors were encountered: