steveloughran commented on pull request #2361:
URL: https://github.com/apache/hadoop/pull/2361#issuecomment-704335369


   tests with markers=keep & delete all good other than
   * continuous read() under-fulfillment breaking tests which expect their 
buffers to always be full. Root cause clearly some networking issue, but where?
   * ITestS3AInputStreamPerformance stream had to be reopened 3 times, rather 
than 1. Didn't come back on a rerun.
   
   ```
   [INFO] Running 
org.apache.hadoop.fs.s3a.auth.delegation.ITestRoleDelegationInFileystem
   [ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
386.753 s <<< FAILURE! - in 
org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance
   [ERROR] 
testDecompressionSequential128K(org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance)
  Time elapsed: 215.757 s  <<< FAILURE!
   java.lang.AssertionError: 
   open operations in
   null expected:<1> but was:<3>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:645)
        at 
org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance.assertOpenOperationCount(ITestS3AInputStreamPerformance.java:189)
        at 
org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance.assertStreamOpenedExactlyOnce(ITestS3AInputStreamPerformance.java:181)
        at 
org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance.testDecompressionSequential128K(ITestS3AInputStreamPerformance.java:324)
   ```
   
   Assumption: again, network playing up.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



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

Reply via email to