-
Notifications
You must be signed in to change notification settings - Fork 552
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
rptest: bump multiplier to 2.0 for test_max_partitions()
#16126
Conversation
44a9138
to
4db885e
Compare
ready for review |
0f8a214
to
c1b002f
Compare
converting to draft to update based on feedback from today's sync mtg |
bb1839d
to
6fd7f05
Compare
PR ready for review. example output in the description |
new failures in https://buildkite.com/redpanda/redpanda/builds/43908#018d1ea6-0a39-4ac0-9cc5-e86795c920dd:
new failures in https://buildkite.com/redpanda/redpanda/builds/43908#018d1ea6-0a30-40f6-8471-6b14ecaa53c5:
new failures in https://buildkite.com/redpanda/redpanda/builds/43908#018d1eb8-088b-4b7d-a664-898bf883da6c:
new failures in https://buildkite.com/redpanda/redpanda/builds/44100#018d322b-c33a-486b-80a3-20aa84ae8352:
|
The failures are all known, so I can force-merge this once we fix the conflicts, @andrewhsu |
6fd7f05
to
90ed602
Compare
rebased with the tip of |
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/44100#018d3253-8c16-42a5-a694-becb78587763 |
Bump latency multiplier (fudge factor) for
test_max_partitions()
from 1.5 to 2.0 and log warning if latency is above expected max latency, i.e. fudge factor 1.0.This is a workaround for addressing issue #15459
example run:
output:
Backports Required
Release Notes