-
Notifications
You must be signed in to change notification settings - Fork 14k
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
KAFKA-3080: Fix ConsoleConsumerTest by checking version when service is started #770
KAFKA-3080: Fix ConsoleConsumerTest by checking version when service is started #770
Conversation
…is started The MessageFormatter being used was only introduced as of 0.9.0.0. The Kafka version in some tests is changed dynamically, sometimes from trunk back to an earlier version, so this option must be set based on the version used when the service is started, not when it is created.
@granders Tracked this down to 9220df9. Verified this fixes the failing test and still passes all of security_rolling_upgrade_test. Maybe @benstopford can sanity check this as well since he was the author on the original patch? And perhaps @gwenshap for final review + commit? |
Thanks for fixing this @ewencp, makes sense to me. |
Looks good, passes locally. Not expecting anything new, but branch builder is running here: |
@granders there were some failures in the branch builder. Are they related? |
@ijuma This failed, but also failed on trunk on 1/17/2016, so I believe it is unrelated
This also failed
Failure was due to a parsing error (parsing statistics choked on a |
Running again here: |
LGTM. It would be great to get this in. |
LGTM |
The MessageFormatter being used was only introduced as of 0.9.0.0. The Kafka
version in some tests is changed dynamically, sometimes from trunk back to an
earlier version, so this option must be set based on the version used when the
service is started, not when it is created.