You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by GitBox <gi...@apache.org> on 2019/03/15 11:02:59 UTC

[GitHub] [servicecomb-pack] coolbeevip opened a new issue #430: Occasional failure TccLoadBalanceSenderTest.participateFailedThenRetry

coolbeevip opened a new issue #430: Occasional failure TccLoadBalanceSenderTest.participateFailedThenRetry 
URL: https://github.com/apache/servicecomb-pack/issues/430
 
 
   alpah server 0.4.0 master
   
   Use `mvn clean install -Pdemo,spring-boot-2`
   
   error log
   ```
   -------------------------------------------------------
    T E S T S
   -------------------------------------------------------
   Running org.apache.servicecomb.pack.omega.connector.grpc.tcc.GrpcTccClientMessageSenderTest
   Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.594 sec - in org.apache.servicecomb.pack.omega.connector.grpc.tcc.GrpcTccClientMessageSenderTest
   Running org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest
   Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.391 sec <<< FAILURE! - in org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest
   participateFailedThenRetry(org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest)  Time elapsed: 2.388 sec  <<< FAILURE!
   java.lang.AssertionError: 
   
   Expected: is <3>
        but: was <4>
           at org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest.participateFailedThenRetry(TccLoadBalanceSenderTest.java:213)
   
   Running org.apache.servicecomb.pack.omega.connector.grpc.LoadBalanceContextBuilderTest
   Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 sec - in org.apache.servicecomb.pack.omega.connector.grpc.LoadBalanceContextBuilderTest
   Running org.apache.servicecomb.pack.omega.connector.grpc.PushBackReconnectRunnableTest
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec - in org.apache.servicecomb.pack.omega.connector.grpc.PushBackReconnectRunnableTest
   Running org.apache.servicecomb.pack.omega.connector.grpc.saga.RetryableMessageSenderTest
   Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec - in org.apache.servicecomb.pack.omega.connector.grpc.saga.RetryableMessageSenderTest
   Running org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalanceSenderWithTLSTest
   Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.579 sec - in org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalanceSenderWithTLSTest
   Running org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest
   Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.497 sec - in org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest
   
   Results :
   
   Failed tests: 
     TccLoadBalanceSenderTest.participateFailedThenRetry:213 
   Expected: is <3>
        but: was <4>
   ```
   
   I found a possible problem in TccLoadBalanceSender.participationStart
   
   ```
     @Override
     public AlphaResponse participationStart(ParticipationStartedEvent participationStartedEvent) {
       do {
         final TccMessageSender messageSender = pickMessageSender();
         Optional<AlphaResponse> response = doGrpcSend(messageSender, participationStartedEvent, new SenderExecutor<ParticipationStartedEvent>() {
           @Override
           public AlphaResponse apply(ParticipationStartedEvent event) {
             return messageSender.participationStart(event);
           }
         });
         if (response.isPresent()) return response.get();
       } while (!Thread.currentThread().isInterrupted());
   
       throw new OmegaException("Failed to send event " + participationStartedEvent + " due to interruption");
     }
   
   ```
   if  response  is empty it will be executed cyclically. May be this reason?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services