Skip to content

Migrate cluster mode tests to normal framework#442

Merged
enjoy-binbin merged 4 commits intovalkey-io:unstablefrom
enjoy-binbin:migrate_clustertest
May 9, 2024
Merged

Migrate cluster mode tests to normal framework#442
enjoy-binbin merged 4 commits intovalkey-io:unstablefrom
enjoy-binbin:migrate_clustertest

Conversation

@enjoy-binbin
Copy link
Member

We currently has two disjoint TCL frameworks:

  1. Normal testing framework, which trigger by runtest, which individually
    launches nodes for testing.
  2. Cluster framework, which trigger by runtest-cluster, which pre-allocates
    N nodes and uses them for testing large configurations.

The normal TCL testing framework is much more readily tested and is also
automatically run as part of the CI for new PRs. The runtest-cluster since
it runs very slowly (cannot be parallelized), it currently only runs in daily
CI, this results in some changes to the cluster not being exposed in PR CI
in time.

This PR migrate the Cluster mode tests to normal framework. Some cluster
tests are kept in runtest-cluster because of timing issues or not yet
supported, we can process them later.

We currently has two disjoint TCL frameworks:
1. Normal testing framework, which trigger by runtest, which individually
launches nodes for testing.
2. Cluster framework, which trigger by runtest-cluster, which pre-allocates
N nodes and uses them for testing large configurations.

The normal TCL testing framework is much more readily tested and is also
automatically run as part of the CI for new PRs. The runtest-cluster since
it runs very slowly (cannot be parallelized), it currently only runs in daily
CI, this results in some changes to the cluster not being exposed in PR CI
in time.

This PR migrate the Cluster mode tests to normal framework. Some cluster
tests are kept in runtest-cluster because of timing issues or not yet
supported, we can process them later.

Signed-off-by: Binbin <[email protected]>
@enjoy-binbin enjoy-binbin force-pushed the migrate_clustertest branch from ae57ba6 to 8906faa Compare May 6, 2024 04:09
@codecov
Copy link

codecov bot commented May 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.83%. Comparing base (4e944ce) to head (e1fb7ed).

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable     #442      +/-   ##
============================================
+ Coverage     68.88%   69.83%   +0.94%     
============================================
  Files           109      109              
  Lines         61793    61793              
============================================
+ Hits          42566    43153     +587     
+ Misses        19227    18640     -587     

see 23 files with indirect coverage changes

Copy link
Member

@madolson madolson left a comment

Choose a reason for hiding this comment

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

Overall LGTM. Assuming after the merge the new tests Ping enabled still work, I would be good to merge this.

Copy link
Member

@madolson madolson left a comment

Choose a reason for hiding this comment

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

LGTM

@enjoy-binbin enjoy-binbin merged commit fdd023f into valkey-io:unstable May 9, 2024
@enjoy-binbin enjoy-binbin deleted the migrate_clustertest branch May 9, 2024 02:14
karthyuom pushed a commit to karthyuom/valkey that referenced this pull request May 13, 2024
We currently has two disjoint TCL frameworks:
1. Normal testing framework, which trigger by runtest, which individually
launches nodes for testing.
2. Cluster framework, which trigger by runtest-cluster, which pre-allocates
N nodes and uses them for testing large configurations.

The normal TCL testing framework is much more readily tested and is also
automatically run as part of the CI for new PRs. The runtest-cluster since
it runs very slowly (cannot be parallelized), it currently only runs in daily
CI, this results in some changes to the cluster not being exposed in PR CI
in time.

This PR migrate the Cluster mode tests to normal framework. Some cluster
tests are kept in runtest-cluster because of timing issues or not yet
supported, we can process them later.

Signed-off-by: Binbin <[email protected]>
Signed-off-by: Karthick Ariyaratnam <[email protected]>
srgsanky pushed a commit to srgsanky/valkey that referenced this pull request May 19, 2024
We currently has two disjoint TCL frameworks:
1. Normal testing framework, which trigger by runtest, which individually
launches nodes for testing.
2. Cluster framework, which trigger by runtest-cluster, which pre-allocates
N nodes and uses them for testing large configurations.

The normal TCL testing framework is much more readily tested and is also
automatically run as part of the CI for new PRs. The runtest-cluster since
it runs very slowly (cannot be parallelized), it currently only runs in daily
CI, this results in some changes to the cluster not being exposed in PR CI
in time.

This PR migrate the Cluster mode tests to normal framework. Some cluster
tests are kept in runtest-cluster because of timing issues or not yet
supported, we can process them later.

Signed-off-by: Binbin <[email protected]>
enjoy-binbin added a commit to enjoy-binbin/valkey that referenced this pull request Jul 14, 2024
It was introduced wrong in valkey-io#442.

Signed-off-by: Binbin <[email protected]>
enjoy-binbin added a commit that referenced this pull request Jul 19, 2024
It was introduced wrong in #442.

Signed-off-by: Binbin <[email protected]>
hwware pushed a commit to hwware/valkey that referenced this pull request Jul 25, 2024
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