Skip to content

Comments

Increase wait time condition for New Master down consecutively test#2612

Merged
enjoy-binbin merged 1 commit intovalkey-io:unstablefrom
sarthakaggarwal97:fix-slave-select-new-master-down-test
Sep 16, 2025
Merged

Increase wait time condition for New Master down consecutively test#2612
enjoy-binbin merged 1 commit intovalkey-io:unstablefrom
sarthakaggarwal97:fix-slave-select-new-master-down-test

Conversation

@sarthakaggarwal97
Copy link
Contributor

With #2604 merged, the Node #10 should eventually replicate node #5 started passing successfully with valgrind, but I guess we are seeing a new daily failure from a New Master down consecutively test that runs shortly after.

Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
@codecov
Copy link

codecov bot commented Sep 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.26%. Comparing base (a47e8fa) to head (7d17907).
⚠️ Report is 2 commits behind head on unstable.

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable    #2612      +/-   ##
============================================
+ Coverage     72.24%   72.26%   +0.01%     
============================================
  Files           127      127              
  Lines         70820    70820              
============================================
+ Hits          51167    51176       +9     
+ Misses        19653    19644       -9     

see 17 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@enjoy-binbin enjoy-binbin merged commit fab2a12 into valkey-io:unstable Sep 16, 2025
53 checks passed
rjd15372 pushed a commit to rjd15372/valkey that referenced this pull request Sep 19, 2025
…alkey-io#2612)

With valkey-io#2604 merged, the `Node valkey-io#10 should eventually replicate node valkey-io#5`
started passing successfully with valgrind, but I guess we are seeing a
new daily failure from a `New Master down consecutively` test that runs
shortly after.

Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
rjd15372 pushed a commit that referenced this pull request Sep 23, 2025
…2612)

With #2604 merged, the `Node #10 should eventually replicate node #5`
started passing successfully with valgrind, but I guess we are seeing a
new daily failure from a `New Master down consecutively` test that runs
shortly after.

Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
hpatro pushed a commit to hpatro/valkey that referenced this pull request Oct 3, 2025
…alkey-io#2612)

With valkey-io#2604 merged, the `Node valkey-io#10 should eventually replicate node valkey-io#5`
started passing successfully with valgrind, but I guess we are seeing a
new daily failure from a `New Master down consecutively` test that runs
shortly after.

Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
Signed-off-by: Harkrishn Patro <harkrisp@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants