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

DBZ-3824 NoClassDefFoundError for junit platform #2574

Merged
merged 2 commits into from Aug 13, 2021

Conversation

jcechace
Copy link
Member

@jcechace jcechace commented Aug 5, 2021

@jcechace
Copy link
Member Author

jcechace commented Aug 5, 2021

Contains also update for junit5 as they did simplify the dependencies lately and surefire/failsafe tend to be sensitive about that.

@jcechace jcechace changed the title NoClassDefFoundError for junit platform DBZ-3824 NoClassDefFoundError for junit platform Aug 5, 2021
@gunnarmorling
Copy link
Member

@jcechace any idea on the test failures?

@jcechace
Copy link
Member Author

jcechace commented Aug 6, 2021

@jcechace any idea on the test failures?

We are correctly tying together versions of Surefire and Failsafe. For whatever reason, it looks like Failsafe is unable to load the entire classpath correctly. I will look into it during the day but I didn't find anything in my brief look yesterday.

@jcechace
Copy link
Member Author

jcechace commented Aug 6, 2021

@gunnarmorling I "lowered" the upgrade to surefire and failsafe M4 which seems to solve both issues locally.

@jcechace
Copy link
Member Author

jcechace commented Aug 6, 2021

@gunnarmorling the next set of failures appears to be unrelated to changes.

@jcechace
Copy link
Member Author

jcechace commented Aug 9, 2021

so the RecordsStreamProducerIT.testEmptyChangesProducesHeartbeat is failing also locally. However at this point I might use some assistance from somebody who knows these test better

@gunnarmorling
Copy link
Member

@jcechace, I recommend you get hold of @jpechane on that one :)

@jpechane
Copy link
Contributor

@jcechace See #2590

@gunnarmorling
Copy link
Member

@jcechace, could you rebase and force-push this one, so to trigger a new build? Thx!

@jcechace
Copy link
Member Author

@gunnarmorling I did so already yesterday after #2590 was merged. However here you go again ;)

@gunnarmorling
Copy link
Member

@jcechace, ok, thx. So I take it the build failures are not related to this change then? Can you work with @jpechane to make sure they are all tracked in Jira? Typically, you should find existing issues by looking for the name of the failing method in question.

@gunnarmorling
Copy link
Member

@jpechane, @jcechace, are the last two remaining test failures unrelated and tracked via Jira issues?

@jpechane
Copy link
Contributor

jpechane commented Aug 12, 2021

@jcechace
Copy link
Member Author

@gunnarmorling can we merge? I'd like to test if this resolves some test run issues through IntelliJ

@gunnarmorling gunnarmorling merged commit 0edfcd9 into debezium:master Aug 13, 2021
@gunnarmorling
Copy link
Member

Applied, thx!

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