Attila Doroszlai created HDDS-5319:
--------------------------------------

             Summary: Intermittent failure in TestSCMUpdateServiceGrpcServer
                 Key: HDDS-5319
                 URL: https://issues.apache.org/jira/browse/HDDS-5319
             Project: Apache Ozone
          Issue Type: Bug
          Components: test
    Affects Versions: 1.2.0
            Reporter: Attila Doroszlai


{{TestSCMUpdateServiceGrpcServer}} is flaky due to relying on scheduling of 
executor in {{CRLClientUpdateHandler}}.

{code:title=https://github.com/elek/ozone-build-results/blob/03f8167ced07d5d5cc6310ad229eae6f196bd820/2021/06/05/8292/unit/hadoop-hdds/server-scm/org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer.txt#L5-L11}
testClientUpdateWithDelayedRevoke(org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer)
  Time elapsed: 5.183 s  <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<0>
  ...
  at 
org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer.testClientUpdateWithDelayedRevoke(TestSCMUpdateServiceGrpcServer.java:191)
{code}

{code:title=https://github.com/adoroszlai/hadoop-ozone/runs/2771810380#step:4:1068}
[INFO] Running 
org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 33.342 
s <<< FAILURE! - in 
org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer
[ERROR] 
testClientUpdateWithDelayedRevoke(org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer)
  Time elapsed: 5.287 s  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<3>
  ...
  at 
org.apache.hadoop.hdds.scm.update.server.TestSCMUpdateServiceGrpcServer.testClientUpdateWithDelayedRevoke(TestSCMUpdateServiceGrpcServer.java:189)
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to