[ https://issues.apache.org/jira/browse/OMID-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607971#comment-17607971 ]
ASF GitHub Bot commented on OMID-226: ------------------------------------- gjacoby126 commented on PR #123: URL: https://github.com/apache/phoenix-omid/pull/123#issuecomment-1254228520 I still can't recreate the issue with TestWorldTimeOracle.testTimestampOraclePanicsWhenTheStorageHasProblems locally, and the code looks fine. I reordered the mock setup to be before component initialization in case there was a race condition. In addition, the extra thread calling next() on the oracle didn't seem necessary so I removed it, which sped up the test. Let's see again if that improves things in TravisCI. > Migrate from mockito-all to mockito-core and clean up test dependencies > ----------------------------------------------------------------------- > > Key: OMID-226 > URL: https://issues.apache.org/jira/browse/OMID-226 > Project: Phoenix Omid > Issue Type: Task > Reporter: Andrew Kyle Purtell > Assignee: Andrew Kyle Purtell > Priority: Major > Fix For: 1.1.0 > > > At some point OMID will upgrade to latest Hadoop 2.10 and HBase 2.4 versions, > and will begin experiencing IncompatibleClassChangeErrors in unit tests due > to a conflict between mockito-all used by OMID and mockito-core used by > Hadoop and HBase. Prepare for this by migrating from mockito-all to > mockito-core now. Clean up test dependencies while at it. > Phoenix itself should perform this migration as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)