somiljain2006 commented on PR #8026: URL: https://github.com/apache/incubator-seata/pull/8026#issuecomment-4502822689
I reproduced the CI failures locally using the same full test command. The failing tests are: org.apache.seata.config.nacos.NacosMockTest io.seata.config.extend.TestConfigFromExtendSPI The failures occur in seata-config-nacos, while my change only affects seata-discovery-nacos. I also verified that isolated module tests pass locally: ./mvnw -pl config/seata-config-nacos -DskipITs test The NacosMockTest failure appears to be timing/startup related: com.alibaba.nacos.api.exception.NacosException: Client not connected, current status:STARTING So this currently looks like an unrelated flaky/full-suite integration issue rather than a regression introduced by the registry IP/port customization change. -- 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]
