Re: [PR] KRaft upgrade tests should only use latest stable mv [kafka]

2024-03-21 Thread via GitHub
jolshan merged PR #15566: URL: https://github.com/apache/kafka/pull/15566 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] KRaft upgrade tests should only use latest stable mv [kafka]

2024-03-21 Thread via GitHub
jolshan commented on PR #15566: URL: https://github.com/apache/kafka/pull/15566#issuecomment-2013196878 For some reason the build retriggered for the description update. Given this is a system test change, I think we don't have to wait for the rebuild. Here is the old build for reference:

Re: [PR] KRaft upgrade tests should only use latest stable mv [kafka]

2024-03-21 Thread via GitHub
ahuang98 commented on PR #15566: URL: https://github.com/apache/kafka/pull/15566#issuecomment-2013184498 Thanks @jolshan, updated the description! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] KRaft upgrade tests should only use latest stable mv [kafka]

2024-03-21 Thread via GitHub
jolshan commented on PR #15566: URL: https://github.com/apache/kafka/pull/15566#issuecomment-2013167459 Thanks for the fix -- small nit in the description. It's not that the version didn't exist, but that we couldn't run the command (likely because there is no supported (stable) MV for

[PR] KRaft upgrade tests should only use latest stable mv [kafka]

2024-03-20 Thread via GitHub
ahuang98 opened a new pull request, #15566: URL: https://github.com/apache/kafka/pull/15566 This should help us avoid testing MVs before the corresponding release exists. We revert back from testing 3.8 in this case since 3.7 is the current stable version. ### Committer Checklist