[ 
https://issues.apache.org/jira/browse/HDFS-11495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894843#comment-15894843
 ] 

Anu Engineer commented on HDFS-11495:
-------------------------------------

[~xyao] Thanks for filing this JIRA. I have opportunistically fixed this issue 
in the HDFS-11451. I have added more wait time as well as increased the RPC 
time out in TestDatanodeStateMachine. Now the test is passing on my dev box. I 
will leave this open in case you would like me to pull that change into this 
JIRA.


> Ozone: Fix TestDatanodeStateMachine#testDatanodeStateContext
> ------------------------------------------------------------
>
>                 Key: HDFS-11495
>                 URL: https://issues.apache.org/jira/browse/HDFS-11495
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: HDFS-7240
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Minor
>
> Running org.apache.hadoop.ozone.container.common.TestDatanodeStateMachine
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.453 sec <<< 
> FAILURE! - in 
> org.apache.hadoop.ozone.container.common.TestDatanodeStateMachine
> testDatanodeStateContext(org.apache.hadoop.ozone.container.common.TestDatanodeStateMachine)
>   Time elapsed: 0.239 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<REGISTER> but was:<GETVERSION>
>       at org.junit.Assert.fail(Assert.java:88)
>       at org.junit.Assert.failNotEquals(Assert.java:743)
>       at org.junit.Assert.assertEquals(Assert.java:118)
>       at org.junit.Assert.assertEquals(Assert.java:144)
>       at 
> org.apache.hadoop.ozone.container.common.TestDatanodeStateMachine.testDatanodeStateContext(TestDatanodeStateMachine.java:220)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to