Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use standard Redis docker image in CI #3246

Merged
merged 4 commits into from
Jun 6, 2024
Merged

Conversation

gerzse
Copy link
Contributor

@gerzse gerzse commented May 24, 2024

Adapt the tests to use the standard Redis docker image where possible, instead of using the Redis Stack image in all places. This way we can run the CI, at least in theory, against different versions of Redis and Redis Stack dockers.

@gerzse gerzse added the maintenance Maintenance (CI, Releases, etc) label May 24, 2024
@tishun
Copy link

tishun commented May 24, 2024

LGTM

Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI, at least in theory, against different versions of Redis and
Redis Stack dockers.
gerzse and others added 2 commits May 27, 2024 10:34
Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.
@@ -2450,6 +2450,7 @@ def try_delete_libs(self, r, *lib_names):
except Exception:
pass

@pytest.mark.redismod
Copy link
Contributor

Choose a reason for hiding this comment

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

You basically skipped those tests with redismod mark, because cluster tests exclude redismod

f"pytest --protocol={protocol} --cov=./ --cov-report=xml:coverage_cluster.xml -W always -m 'not onlynoncluster and not redismod' --redis-url={cluster_url} --junit-xml=cluster-uvloop-results.xml --uvloop"

It's not critical for these tests because T&F is deprecated anyway, but be careful with it in the future.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, exactly. This is until we get the next release for Stack, at that time hopefully these can be re-enabled in some form.

@gerzse gerzse merged commit ff7821d into redis:master Jun 6, 2024
46 checks passed
gerzse added a commit to gerzse/redis-py that referenced this pull request Jul 11, 2024
Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI against different versions of Redis and Redis Stack.

Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.

---------

Co-authored-by: Gabriel Erzse <gabriel.erzse@redis.com>
gerzse added a commit that referenced this pull request Jul 11, 2024
Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI against different versions of Redis and Redis Stack.

Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.

---------

Co-authored-by: Gabriel Erzse <gabriel.erzse@redis.com>
agnesnatasya pushed a commit to agnesnatasya/redis-py that referenced this pull request Jul 20, 2024
Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI against different versions of Redis and Redis Stack.

Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.

---------

Co-authored-by: Gabriel Erzse <gabriel.erzse@redis.com>
vladvildanov pushed a commit that referenced this pull request Sep 27, 2024
Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI against different versions of Redis and Redis Stack.

Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.

---------

Co-authored-by: Gabriel Erzse <gabriel.erzse@redis.com>
vladvildanov pushed a commit that referenced this pull request Sep 27, 2024
Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI against different versions of Redis and Redis Stack.

Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.

---------

Co-authored-by: Gabriel Erzse <gabriel.erzse@redis.com>
vladvildanov pushed a commit that referenced this pull request Sep 27, 2024
Adapt the tests to use the standard Redis docker image where possible,
instead of using the Redis Stack image in all places. This way we can
run the CI against different versions of Redis and Redis Stack.

Run the test cluster based on the default Redis docker image, i.e.
without Stack support. This is needed in order to make the CI pass until
Stack gets a new release. What is needed is to mark all Stack related
tests accordingly, and then they don't get executed in the cluster
tests (they are already filtered out in `invoke cluster-tests`).

Take the opportunity to remove some empty tests and to fix the naming in
two tests.

---------

Co-authored-by: Gabriel Erzse <gabriel.erzse@redis.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Maintenance (CI, Releases, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants