AlbumenJ commented on PR #15113:
URL: https://github.com/apache/dubbo/pull/15113#issuecomment-2677284543

   > `Build and Test Scheduled On 3.3` 
https://github.com/apache/dubbo/actions/runs/13269479987/job/37046175125 which 
just runned after this PR merging into 3.3:
   > 
   > ```
   > 2025-02-11T18:39:00.4118796Z [ERROR] Errors: 
   > 2025-02-11T18:39:00.4124586Z [ERROR]   
ServiceConfigTest.testMethodConfigWithConfiguredArgumentType:492 » Rpc Fail to 
start server(url: 
dubbo://10.1.0.109:20880/org.apache.dubbo.config.api.DemoService?anyhost=true&application=app&background=false&bind.ip=10.1.0.109&bind.port=20880&channel.readonly.sent=true&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&executor-management-mode=isolation&export=true&file-cache=true&generic=false&heartbeat=60000&interface=org.apache.dubbo.config.api.DemoService&methods=callInnerClass,echo,getBox,getUsers,sayName,throwDemoException&pid=236894&register=false&release=3.3.4-SNAPSHOT&sayName.0.callback=false&sayName.return=true&sayName.sent=true&side=provider&timestamp=1739299104130)
 Failed to bind NettyServer on /0.0.0.0:20880, cause: Address already in use
   > 2025-02-11T18:39:00.4131440Z [ERROR]   
MultipleRegistryCenterServiceDiscoveryRegistryIntegrationTest.integrate:152 » 
Runtime org.apache.dubbo.rpc.RpcException: Fail to start server(url: 
dubbo://10.1.0.109:20880/org.apache.dubbo.config.integration.multiple.servicediscoveryregistry.MultipleRegistryCenterServiceDiscoveryRegistryService?anyhost=true&application=multiple-registry-center-provider-for-service-discovery-registry-protocol&async=false&background=false&bind.ip=10.1.0.109&bind.port=20880&channel.readonly.sent=true&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&executor-management-mode=isolation&file-cache=true&generic=false&heartbeat=60000&interface=org.apache.dubbo.config.integration.multiple.servicediscoveryregistry.MultipleRegistryCenterServiceDiscoveryRegistryService&methods=hello&pid=236894&prefer.serialization=hessian2,fastjson2&release=3.3.4-SNAPSHOT&service-name-mapping=true&side=provider&timestamp=1739299132226)
 Failed to bind NettyServer on /0.0.0.0:20880,
  cause: Address already in use
   > ```
   
   Maybe we should enhance the UT


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