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

ASF GitHub Bot commented on HADOOP-18641:
-----------------------------------------

steveloughran commented on PR #5429:
URL: https://github.com/apache/hadoop/pull/5429#issuecomment-1443610860

   HDFS failures, all of which I consider to be race conditions/timing issues 
and so not blockers.
   
   ## TestDataNodeRollingUpgrade.deleteAndEnsureInTrash
   
   ```
   java.lang.AssertionError
        at org.junit.Assert.fail(Assert.java:87)
        at org.junit.Assert.assertTrue(Assert.java:42)
        at org.junit.Assert.assertTrue(Assert.java:53)
        at 
org.apache.hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade.deleteAndEnsureInTrash(TestDataNodeRollingUpgrade.java:141)
        at 
org.apache.hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade.testWithLayoutChangeAndRollback(TestDataNodeRollingUpgrade.java:420)
   ```
   
   is an assert after some heartbeats
   ```
       triggerHeartBeats();
       assertTrue(trashFile.exists());  // here
       assertFalse(blockFile.exists());
   ```
   The file was deleted, just didn't show up
   
   ## TestBalancerWithHANameNodes.testBalancerWithObserverWithFailedNode: 
timeout
   ```
   
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes.testBalancerWithObserverWithFailedNode
   
   Failing for the past 1 build (Since #4 )
   Took 3 min 0 sec.
   Error Message
   test timed out after 180000 milliseconds
   Stacktrace
   org.junit.runners.model.TestTimedOutException: test timed out after 180000 
milliseconds
   ```
     
     
   ## TestDFSAdmin.testAllDatanodesReconfig
   
   race condition; created https://issues.apache.org/jira/browse/HDFS-16934
   
   ## TestFsDatasetImpl.testReportBadBlocks
   
   ```
   Failing for the past 1 build (Since #4 )
   Took 7.4 sec.
   Error Message
   expected:<1> but was:<0>
   Stacktrace
   java.lang.AssertionError: expected:<1> but was:<0>
        at org.junit.Assert.fail(Assert.java:89)
        at org.junit.Assert.failNotEquals(Assert.java:835)
        at org.junit.Assert.assertEquals(Assert.java:647)
        at org.junit.Assert.assertEquals(Assert.java:633)
   ```
   
   assert is after a 3s sleep waiting for reports coming in. Going to brittle 
against delays. creating a jira; LambdaTestUtils.eventually() should be used 
around this assert
   
   ```
         dataNode.reportBadBlocks(block, dataNode.getFSDataset()
             .getFsVolumeReferences().get(0));
         Thread.sleep(3000);                                           // 3s 
sleep
         BlockManagerTestUtil.updateState(cluster.getNamesystem()
             .getBlockManager());
         // Verify the bad block has been reported to namenode
         Assert.assertEquals(1, 
cluster.getNamesystem().getCorruptReplicaBlocks());  // here
   ```
   
   
   
   




> cyclonedx maven plugin breaks builds on recent maven releases (3.9.0)
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-18641
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18641
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.4.0, 3.3.5, 3.3.9
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.5, 3.3.9
>
>
> having upgraded maven to get spark to build, the cyclonedx plugin for 
> HADOOP-18590 is failing. see SPARK-42380 for the same.
> the 3.3.5 RCs are building with the older maven version of our docker images, 
> but if we release as is we will ship something which will get harder over 
> time to build.
> reverting HADOOP-18590 everywhere. sorry.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to