zrlw opened a new issue, #15416:
URL: https://github.com/apache/dubbo/issues/15416

   ### Pre-check
   
   - [x] I am sure that all the content I provide is in English.
   
   
   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache Dubbo Component
   
   Java SDK (apache/dubbo)
   
   ### Dubbo Version
   
   dubbo 3.3.4
   
   ### Steps to reproduce this issue
   
   refer to dubbo-samples/dubbo-servicediscovery-migration
   1. start provider1 and provider2 of dubbo-servicediscovery-migration
   2. run DemoServiceIT
   sometimes the method testApplication might fail because:
   1. each service migration notice only occurred at it's first calling time.
   2. the new step of each service first migration notice is always 
```FORCE_INTERFACE``` which was set at first test case - 
DemoServiceIT#testInterface, it's the root cause of this trouble.
   see details at 
https://github.com/apache/dubbo-samples/actions/runs/15293293194/job/43016875948
   
![Image](https://github.com/user-attachments/assets/8a2cf925-0292-4968-a9ae-e1a31b51fab8)
   
   ### What you expected to happen
   
   the new step of each service first migration notice should be the step that 
was set by current test case.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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