ci: switches memcached image to bitnamisecure image #6583
+23
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dosubot
bot
added
size:S
Xuanwo
reviewed
Sep 22, 2025
Comment on lines
+29
to
+40
| - name: Print memcached logs on failure | ||
| if: failure() | ||
| shell: bash | ||
| working-directory: fixtures/memcached | ||
| run: | | ||
| echo "==== docker ps -a ====" | ||
| docker ps -a | ||
| echo "==== docker logs memcached-memcached-1 ====" | ||
| docker logs memcached-memcached-1 || true | ||
| echo "==== docker compose logs ====" | ||
| docker compose -f docker-compose-memcached-with-auth.yml logs || true | ||
There was a problem hiding this comment.
There still seems to be a problem with the bitnamisecure/memcached image, but I haven't figured out exactly what's going on, the authentication doesn't seem to be reporting errors anymore, but the tests are timing out a ton!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Related #6435.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?