[ https://issues.apache.org/jira/browse/HDFS-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655251#comment-13655251 ]
Hudson commented on HDFS-4751: ------------------------------ Integrated in Hadoop-Hdfs-trunk #1395 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1395/]) HDFS-4751. TestLeaseRenewer#testThreadName flakes. Contributed by Andrew Wang. (Revision 1481160) Result = FAILURE atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1481160 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/LeaseRenewer.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestLeaseRenewer.java > TestLeaseRenewer#testThreadName flakes > -------------------------------------- > > Key: HDFS-4751 > URL: https://issues.apache.org/jira/browse/HDFS-4751 > Project: Hadoop HDFS > Issue Type: Bug > Components: test > Affects Versions: 3.0.0, 2.0.5-beta > Reporter: Andrew Wang > Assignee: Andrew Wang > Priority: Minor > Fix For: 2.0.5-beta > > Attachments: hdfs-4751-1.patch, hdfs-4751-2.patch > > > Seen internally and during upstream trunk builds, error like the following: > {noformat} > Error Message: > Unfinished stubbing detected here: -> at > org.apache.hadoop.hdfs.TestLeaseRenewer.testThreadName(TestLeaseRenewer.java:197) > E.g. thenReturn() may be missing. Examples of correct stubbing: > when(mock.isOk()).thenReturn(true); > when(mock.isOk()).thenThrow(exception); > doThrow(exception).when(mock).someVoidMethod(); Hints: 1. missing > thenReturn() 2. although stubbed methods may return mocks, you cannot inline > mock creation (mock()) call inside a thenReturn method (see issue 53) > Stack Trace: > org.mockito.exceptions.misusing.UnfinishedStubbingException: > Unfinished stubbing detected here: > -> at > org.apache.hadoop.hdfs.TestLeaseRenewer.testThreadName(TestLeaseRenewer.java:197) > {noformat} > I believe it's due to mocking while being concurrently accessed by another > thread. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira