mjsax commented on PR #14539: URL: https://github.com/apache/kafka/pull/14539#issuecomment-1773534318
Just looked into the branch builder results for `test_compatible_brokers_eos_v2_enabled` 2.6.3 in more details. Broker log shows: ``` bash: /opt/kafka-2.6.3/bin/kafka-server-start.sh: No such file or directory ``` And the console output show ``` worker4: + get_kafka 2.6.2 2.12 17:45:33 worker4: + version=2.6.2 17:45:33 worker4: + scala_version=2.12 17:45:33 worker4: + kafka_dir=/opt/kafka-2.6.2 17:45:33 worker4: + url=https://s3-us-west-2.amazonaws.com/kafka-packages/kafka_2.12-2.6.2.tgz 17:45:33 worker4: + url_streams_test=https://s3-us-west-2.amazonaws.com/kafka-packages/kafka-streams-2.6.2-test.jar 17:45:33 worker4: + '[' '!' -d /opt/kafka-2.6.2 ']' 17:45:33 worker4: /tmp /opt/jdk/8 17:45:33 worker4: + pushd /tmp 17:45:33 worker4: + curl --retry 5 -O https://s3-us-west-2.amazonaws.com/kafka-packages/kafka_2.12-2.6.2.tgz ``` The `Dockerfile` does use `2.6.3` though -- not sure where `2.6.2` come from? Can it be that this PR should have been rebased to pickup some `Dockerfile` updates I did recently (https://github.com/apache/kafka/commit/cdf726fd358f9be3438ceefb01073ab40a31a8b4) Maybe we should keep observing `trunk` runs and see what it does... Given that it's always 2.6.2, 2.7.3, and 3.3.2 that failed above, and that's exactly the versions the other PR bumped, I see a clear relationship. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
