Re: [I] Mockito-inline has conflict with docker Image [hudi]

["rangareddy (via GitHub)" <gi...@apache.org>]

rangareddy commented on issue #16620:
URL: https://github.com/apache/hudi/issues/16620#issuecomment-5068167147

   This issue was reviewed as part of the JIRA-migrated backlog triage.
   
   Findings: This tracks a build/CI constraint rather than a product defect: adding `mockito-inline` to `hudi-tests-common` triggers a ByteBuddy agent self-attachment failure (`UnsatisfiedLinkError: [libattach.so](http://libattach.so/) already loaded in another classloader`) under the JDK 1.8 Azure CI Docker image. On current master the constraint is still worked around -- `hudi-tests-common` declares only `mockito-core` and `mockito-junit-jupiter` (mockito 5.21.0), not `mockito-inline` -- so no merged change resolves the underlying conflict. If a test that must run inside the Docker image needs inline mocking, the ByteBuddy/JDK agent-attachment conflict would still have to be solved (or the Docker image's JDK upgraded). 
   
   Keeping open as an unresolved build/CI item.


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org