Alanxtl opened a new issue, #3824: URL: https://github.com/apache/dubbo-go/issues/3824
Related to #3614 (items 1 and 2). ### What happened? `TestFailbackRetryFailed` and `TestFailbackOutOfLimit` are still listed in `RACE_SKIP_TESTS`, even though the original `lastT` and ticker races were addressed by #3599. Both tests passed three targeted runs under `-race` on `develop` at `6ea4f0817299973c5e17e73fea3710cf528c1426` with Go 1.26.3 on Windows. The current skip still prevents the normal race suite from exercising them. ### Verification ```sh go test -race -count=10 ./cluster/cluster/failback -run '^(TestFailbackRetryFailed|TestFailbackOutOfLimit)$' ``` ### Expected outcome - Verify both tests are reliable under the race detector, including the relevant package/suite context. - Remove both names from `RACE_SKIP_TESTS` and confirm the project's race CI command executes them without reporting their original races. -- 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]
