Skip to content

Fix weekly workflow to continue after failure in releases branches#3082

Merged
enjoy-binbin merged 1 commit into
valkey-io:unstablefrom
sarthakaggarwal97:allow-fail-fast-weekly-runs
Jan 21, 2026
Merged

Fix weekly workflow to continue after failure in releases branches#3082
enjoy-binbin merged 1 commit into
valkey-io:unstablefrom
sarthakaggarwal97:allow-fail-fast-weekly-runs

Conversation

@sarthakaggarwal97

Copy link
Copy Markdown
Contributor

Currently, the weekly runs do not progress if there is a failed workflow as github CI treats fail-fast to be true by default. With this change, we continue to test all the branches even after failure.

Last week's run: https://github.com/valkey-io/valkey/actions/runs/21107098709
Documentation on fail-fast: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idstrategyfail-fast

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

codecov Bot commented Jan 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.25%. Comparing base (8fdc9e6) to head (3eebc9e).
⚠️ Report is 4 commits behind head on unstable.

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable    #3082      +/-   ##
============================================
- Coverage     74.41%   74.25%   -0.17%     
============================================
  Files           129      129              
  Lines         71009    71009              
============================================
- Hits          52844    52728     -116     
- Misses        18165    18281     +116     

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.

@sarthakaggarwal97 sarthakaggarwal97 changed the title Fix weekly workflow to continue runs failure in releases branches Fix weekly workflow to continue after failure in releases branches Jan 20, 2026

@roshkhatri roshkhatri left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, Also why does the workflow only run for 7.2 branch?

Is it because fail-fast?

@sarthakaggarwal97

sarthakaggarwal97 commented Jan 20, 2026

Copy link
Copy Markdown
Contributor Author

@roshkhatri yes. I have set the max-parallel as 1, which essentially allows 1 branch at a time, so that we don't exhaust all valkey CI runners running all the branches together. But if any of the branch runs fails, the subsequent runs are cancelled.

@roshkhatri

Copy link
Copy Markdown
Member

Oh got it, cause of max-parallel: 1
Why cant we remove the max limitations?

@sarthakaggarwal97

Copy link
Copy Markdown
Contributor Author

Why cant we remove the max limitations?

To avoid blocking all the github runners. Might block CI runs for the PRs I guess.

@roshkhatri

Copy link
Copy Markdown
Member

If we remove the max-parallel it should queue the jobs and start workflows as the runners are available

@roshkhatri

Copy link
Copy Markdown
Member

I mean we are anyway blocking the runners with the 40-45 wfs, and once any of them finishes then the CI will be given runners.

@Nikhil-Manglore Nikhil-Manglore left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good change to have

@enjoy-binbin enjoy-binbin merged commit 951d942 into valkey-io:unstable Jan 21, 2026
37 of 38 checks passed
arshidkv12 pushed a commit to arshidkv12/valkey that referenced this pull request Jan 23, 2026
…alkey-io#3082)

Currently, the weekly runs do not progress if there is a failed workflow
as github CI treats `fail-fast` to be true by default. With this change,
we continue to test all the branches even after failure.

Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
Signed-off-by: arshidkv12 <arshidkv12@gmail.com>
harrylin98 pushed a commit to harrylin98/valkey_forked that referenced this pull request Feb 19, 2026
…alkey-io#3082)

Currently, the weekly runs do not progress if there is a failed workflow
as github CI treats `fail-fast` to be true by default. With this change,
we continue to test all the branches even after failure.

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

Currently, the weekly runs do not progress if there is a failed workflow
as github CI treats `fail-fast` to be true by default. With this change,
we continue to test all the branches even after failure.

Signed-off-by: Sarthak Aggarwal <sarthagg@amazon.com>
Signed-off-by: Harkrishn Patro <bunty.hari@gmail.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.

5 participants