Skip to content
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

JUnit test not working in Windows #9

Closed
jukkakarvanen opened this issue Mar 28, 2019 · 2 comments
Closed

JUnit test not working in Windows #9

jukkakarvanen opened this issue Mar 28, 2019 · 2 comments

Comments

@jukkakarvanen
Copy link
Contributor

The JUnit test are failing in Windows due to https://issues.apache.org/jira/browse/KAFKA-6647

The same problem seems to be also mentioned here:
#4 (comment)

Readme also state: "Kafka does not support and work well on Windows, this is not tested at all."

I have used this kind of Workaround to get JUnit tests to work in Windows:
https://github.com/jukkakarvanen/kafka-streams-machine-learning-examples/tree/junit_in_windows

Not sure is this worth merging, but anyway if you want to run test in Windows you can use that branch.

NOTE: This is changed only in test code, not in actual classes.

@kaiwaehner
Copy link
Owner

I merged it. Hopefully https://issues.apache.org/jira/browse/KAFKA-6647 will be fixed soon, then we can remove your workaround and just use the regular Kafka Streams test classes.

As side note: Confluent recommends to NOT use Kafka and especially Kafka Streams on Windows. We have seen several issues and (strange) errors and inconsistencies.

@jukkakarvanen
Copy link
Contributor Author

Yes, currently I am used to develop with IntelliJ IDEA in Windows. Now with this fix you can run the test easily in IDE before launching application inside Docker Linux container.

The application is still failing with exception in cleanup method in Window, but for me it does not matter because I run it inside Docker anyway to avoid the problems you mentioned.

It would be easy to fix actual application removing the cleanup, because it is only "development time workaround" and to my understanding these examples does not contain anything to cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants