-
Notifications
You must be signed in to change notification settings - Fork 589
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
update ducktape version #13116
update ducktape version #13116
Conversation
a9d84fb
to
8756be5
Compare
/ci-repeat 2 |
1 similar comment
/ci-repeat 2 |
30258c4
to
e78ab7e
Compare
/ci-repeat 2 |
e78ab7e
to
434f5b6
Compare
/ci-repeat 2 |
434f5b6
to
53b84ad
Compare
/cdt |
/cdt |
/cdt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I triggered a scale test to make sure that the parametrization (done in redpanda-data/ducktape#24) works. The failure is known #13183... it didn't fail due to ducktape
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
i verified the rebase on our fork was on top of the 0.8.18 upstream release. comparison of upstream changes from what we had before: confluentinc/ducktape@v0.8.8...v0.8.18
53b84ad
to
f043bc4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was the master branch force-pushed?
I usually find that it's clearer to create a new branch, something like v23.3.x
or redpanda-v23.3.x
.
I guess we also need this: redpanda-data/ducktape@62e0285 ?
f043bc4
to
45cff55
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was the master branch force-pushed?
I usually find that it's clearer to create a new branch, something like
v23.3.x
orredpanda-v23.3.x
.
yeah it was force-pushed to master
. The structure of the ducktape repo will eventually change. the plan is described https://github.com/redpanda-data/devprod/issues/836
I guess we also need this: redpanda-data/ducktape@62e0285 ?
fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the update to redpanda-data/ducktape git commit LGTM, but why is apache/kafka git commit required for change?
also fyi redpanda-data/ducktape#27 (review)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the update to redpanda-data/ducktape git commit LGTM, but why is apache/kafka git commit required for change?
also fyi redpanda-data/ducktape#27 (review)
the older version of kafkatest, depends on ducktape 0.8.8. the new one depends on ducktape >0.8
45cff55
to
28f0c6d
Compare
rebased with upstream v0.8.x ref redpanda-data/platform-devprod#332
28f0c6d
to
a9a2a84
Compare
the older version of kafkatest, depends on ducktape 0.8.8. the new one depends on ducktape >0.8
a9a2a84
to
0c3de07
Compare
Our fork of ducktape was rebased on top of 0.8.x. This PR updates the ducktape version.
It also updates the kafkatest version, since the older version of kafkatest, depends on
ducktape 0.8.8. the new one depends on
ducktape >0.8
ref https://github.com/redpanda-data/devprod/issues/332
Backports Required
Release Notes