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

Nemanja Matkovic commented on HDFS-9266:
----------------------------------------

For test case failures:
   - TestBlockManager.testBlocksAreNotUnderreplicatedInSingleRack -->  Same 
test case failure in same way in Hdfs-trunk build # 2448 ==> This is flaky test
   - TestNodeCount.testNodeCount --> I see same test case failure in same way 
in Hdfs-trunk build # 2448 ==> This is flaky test
   - TestRecoverStripedFile --> We are based after Erasure Encoding got merged 
into trunk, this was failing then, so we have failures here, not regression by 
these changes.
   - TestReplaceDatanodeOnFailure --> I see same test case failure in same way 
in Hdfs-trunk build # 2452 ==> This is flaky test
   - TestWriteReadStripedFile --> We are based after Erasure Encoding got 
merged into trunk, this was failing then, so we have failures here, not 
regression by these changes.
   - TestFileTruncate --> Flaky test, tracked by jira HDFS-9224
   - TestRollingUpgrade --> I see same test suite (not test case) failure in 
same way in Hdfs-trunk build # 2454 ==> Might be that this is flaky test, will 
see with next patch if it passes.
   - TestNameNodeRespectsBindHostKeys --> This one is my bad, forgot to test on 
IPv4 only machine after adding test cases, will upload new patch soon


> hadoop-hdfs - Avoid unsafe split and append on fields that might be IPv6 
> literals
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-9266
>                 URL: https://issues.apache.org/jira/browse/HDFS-9266
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: Nemanja Matkovic
>            Assignee: Nemanja Matkovic
>              Labels: ipv6
>         Attachments: HDFS-9266-HADOOP-11890.1.patch, 
> HDFS-9266-HADOOP-11890.2.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to