valkey icon indicating copy to clipboard operation
valkey copied to clipboard

Weekly Test Runs on Released Branches

Open sarthakaggarwal97 opened this issue 2 months ago • 5 comments

Resolves: https://github.com/valkey-io/valkey/issues/2228

Visualization: https://github.com/sarthakaggarwal97/valkey/actions/runs/19113712295

Currently, there are no tests running on the already released branches. We often do backport for bug fixes and CVEs in these older versions, and end up with multiple CI tests failures on these branches.

The PR adds support for running weekly tests on already released versions >= 7.2. The workflow will execute the "daily" test workflow for each of these branches on Sunday 06:00 UTC.

The idea is to continuously monitor our released versions through weekly test runs (during the time when is lesser activity on github runners).

sarthakaggarwal97 avatar Oct 07 '25 04:10 sarthakaggarwal97

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 72.45%. Comparing base (32844b8) to head (45a2e7c). :warning: Report is 41 commits behind head on unstable.

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable    #2702      +/-   ##
============================================
+ Coverage     72.41%   72.45%   +0.03%     
============================================
  Files           128      128              
  Lines         70261    70487     +226     
============================================
+ Hits          50879    51069     +190     
- Misses        19382    19418      +36     

see 30 files with indirect coverage changes

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

codecov[bot] avatar Oct 10 '25 01:10 codecov[bot]

@hpatro @roshkhatri I added a link in the PR description to visualize the test. Currently, it only ran for 8.0 and 8.1 in my fork, because I only had those branches in my fork. In valkey repo, it should be running on all the Valkey released branches. Please take a look.

Do they conflict with each other or they just run in queued manner.

They run in a queued manner.

sarthakaggarwal97 avatar Nov 05 '25 20:11 sarthakaggarwal97

Can you also add screen shots of the workflow runs as an example in the top comment??

roshkhatri avatar Nov 11 '25 19:11 roshkhatri

@roshkhatri there is a link in the top comment to display how it looks like. PS: It only ran on 8.0 and 8.1 branches because locally I had fetched only those two branches.

sarthakaggarwal97 avatar Nov 11 '25 20:11 sarthakaggarwal97

@madolson please help review whenever you get a chance! Thank you!

sarthakaggarwal97 avatar Nov 21 '25 00:11 sarthakaggarwal97