lokidundun opened a new issue, #8000:
URL: https://github.com/apache/incubator-seata/issues/8000

   ### Check Ahead
   
   - [x] I have searched the [issues](https://github.com/seata/seata/issues) of 
this repository and believe that this is not a duplicate.
   
   - [ ] I am willing to try to fix this bug myself.
   
   
   ### Ⅰ. Issue Description
   
   Error:  Failures: 
   ```
   Error:    
NacosRegistryServiceImplTest.shouldNotOverwriteClusterWhenEventHasEmptyInstanceList:389->captureSubscribedListener:413
 
   Argument(s) are different! Wanted:
   namingService.subscribe(
       "MOCKED_APP",
       "MOCKED_GROUP",
       [MOCKED_CLUSTER_EMPTY],
       <Capturing argument>
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImplTest.captureSubscribedListener(NacosRegistryServiceImplTest.java:413)
   Actual invocations have different arguments:
   namingService.getAllInstances(
       "seata-server",
       "SEATA_GROUP",
       [MOCKED_CLUSTER_EMPTY]
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.lookup(NacosRegistryServiceImpl.java:192)
   namingService.subscribe(
       "seata-server",
       "SEATA_GROUP",
       [MOCKED_CLUSTER_EMPTY],
       
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl$$Lambda$451/0x00007fdfd828dc88@6e9a0bea
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.subscribe(NacosRegistryServiceImpl.java:143)
   ```
   
   ```
   Error:    NacosRegistryServiceImplTest.shouldRegisterSuccessfully:187 
   Argument(s) are different! Wanted:
   namingService.registerInstance(
       "MOCKED_APP",
       "MOCKED_GROUP",
       "127.0.0.1",
       8091,
       "MOCKED_CLUSTER"
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImplTest.shouldRegisterSuccessfully(NacosRegistryServiceImplTest.java:187)
   Actual invocations have different arguments:
   namingService.registerInstance(
       "seata-server",
       "SEATA_GROUP",
       "127.0.0.1",
       8091,
       "default"
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.register(NacosRegistryServiceImpl.java:118)
   ```
   
   ```
   Error:    NacosRegistryServiceImplTest.shouldSubscribeAndStoreListener:231 
   Argument(s) are different! Wanted:
   namingService.subscribe(
       "MOCKED_APP",
       "MOCKED_GROUP",
       [MOCKED_CLUSTER_A],
       Mock for EventListener, hashCode: 1402400433
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImplTest.shouldSubscribeAndStoreListener(NacosRegistryServiceImplTest.java:231)
   Actual invocations have different arguments:
   namingService.subscribe(
       "seata-server",
       "SEATA_GROUP",
       [MOCKED_CLUSTER_A],
       Mock for EventListener, hashCode: 1402400433
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.subscribe(NacosRegistryServiceImpl.java:143)
   ```
   
   ```
   Error:    
NacosRegistryServiceImplTest.shouldSubscribeClusterWhenNotExistInListenerMap:357->captureSubscribedListener:413
 
   Argument(s) are different! Wanted:
   namingService.subscribe(
       "MOCKED_APP",
       "MOCKED_GROUP",
       [MOCKED_CLUSTER_E],
       <Capturing argument>
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImplTest.captureSubscribedListener(NacosRegistryServiceImplTest.java:413)
   Actual invocations have different arguments:
   namingService.getAllInstances(
       "seata-server",
       "SEATA_GROUP",
       [MOCKED_CLUSTER_E]
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.lookup(NacosRegistryServiceImpl.java:192)
   namingService.subscribe(
       "seata-server",
       "SEATA_GROUP",
       [MOCKED_CLUSTER_E],
       
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl$$Lambda$451/0x00007fdfd828dc88@629075f4
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.subscribe(NacosRegistryServiceImpl.java:143)
   ```
   
   ```
   Error:    NacosRegistryServiceImplTest.shouldUnregisterSuccessfully:209 
   Argument(s) are different! Wanted:
   namingService.deregisterInstance(
       "MOCKED_APP",
       "MOCKED_GROUP",
       "127.0.0.1",
       8091,
       "MOCKED_CLUSTER"
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImplTest.shouldUnregisterSuccessfully(NacosRegistryServiceImplTest.java:209)
   Actual invocations have different arguments:
   namingService.deregisterInstance(
       "seata-server",
       "SEATA_GROUP",
       "127.0.0.1",
       8091,
       "default"
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.unregister(NacosRegistryServiceImpl.java:130)
   ```
   
   ```
   Error:    NacosRegistryServiceImplTest.shouldUnsubscribeSuccessfully:252 
   Argument(s) are different! Wanted:
   namingService.unsubscribe(
       "MOCKED_APP",
       "MOCKED_GROUP",
       [MOCKED_CLUSTER_B],
       Mock for EventListener, hashCode: 2077462509
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImplTest.shouldUnsubscribeSuccessfully(NacosRegistryServiceImplTest.java:252)
   Actual invocations have different arguments:
   namingService.unsubscribe(
       "seata-server",
       "SEATA_GROUP",
       [MOCKED_CLUSTER_B],
       Mock for EventListener, hashCode: 2077462509
   );
   -> at 
org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.unsubscribe(NacosRegistryServiceImpl.java:157)
   ```
   
   
   
   ### Ⅱ. Describe what happened
   
   No response
   
   ### Ⅲ. Describe what you expected to happen
   
   No response
   
   ### Ⅳ. How to reproduce it (as minimally and precisely as possible)
   
   No response
   
   ### Ⅴ. Anything else we need to know?
   
   No response
   
   ### Ⅵ. Environment
   
   No response


-- 
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.

To unsubscribe, e-mail: [email protected]

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