WIP Automate smoke tests #33
Open
Conversation
This file contains 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
solsson
pushed a commit
that referenced
this pull request
Oct 24, 2023
Adjust logging and allow for log level filtering via env KAFKA_KEYVAL…
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.
Automated builds still can't run our integration tests (that do work with local docker builds) quite possibly because builds are resource capped and rather heavy already.
Docker Hub has support for Automated tests however, which documents a limit of 2GB memory. It should be possible to squeeze Zookeeper + Kafka + a native KKV build into 2GB. Initial ambition could be to check that the image can be started and the container starts polling.
Such validation works at 1bfe25d with
docker-compose -f docker-compose.test.yml -f docker-compose.dev-overrides.yml up --build topic1-create sutbut we need to deal with validation and termination.