This matches a potential future max message size in the production kafka
clusters.
Depends on D2961.
Details
Details
- Reviewers
ardumont - Group Reviewers
Reviewers - Commits
- rDJNL17d64ff61bcf: Set a larger max message size for the kafka used in journal tests
no test added for now
Diff Detail
Diff Detail
- Repository
- rDJNL Journal infrastructure
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Comment Actions
Build is green
Patch application report for D2962 (id=10545)
Could not rebase; Attempt merge onto 7d6ead58a4...
Updating 7d6ead5..17d64ff Fast-forward swh/journal/tests/conftest.py | 10 ++++++++-- swh/journal/tests/test_kafka_writer.py | 30 +++++++++++++++++++++++------- 2 files changed, 31 insertions(+), 9 deletions(-)
Changes applied before test
commit 17d64ff61bcf7ff0c8849cb0787ef10b97d7aa7f
Author: Nicolas Dandrimont <nicolas@dandrimont.eu>
Date: Mon Apr 6 19:14:38 2020 +0200
Set a larger max message size for the kafka used in journal tests
This matches a potential future max message size in the production kafka
clusters.
commit 4aca80d0e313d716cfa1dd4149d7ad0e8c28c44f
Author: Nicolas Dandrimont <nicolas@dandrimont.eu>
Date: Mon Apr 6 18:56:46 2020 +0200
Split kafka writer tests into a consumer loop and an object check
This makes the consumer loop easier to reuse in other more specific testsSee https://jenkins.softwareheritage.org/job/DJNL/job/tests-on-diff/15/ for more details.