Alanxtl opened a new issue, #3823:
URL: https://github.com/apache/dubbo-go/issues/3823

   Related to #3614 (items 7 and 8).
   
   ### What happened?
   
   The originally reported `httpSrv` / `http3Srv` pointer race was fixed in 
#3639. However, repeatedly running the two affected server tests together can 
still fail under `-race` due to a different conflict:
   
   - A later test creates a new instance and calls `gostLogger.SetLogger` 
during `InstanceOptions.initGlobalLogger`.
   - A Triple health-watch goroutine from an earlier call logs through `gost` 
concurrently.
   
   On `develop` at `6ea4f0817299973c5e17e73fea3710cf528c1426`, Go 1.26.3 on 
Windows, the race detector reported 
`github.com/dubbogo/gost/log/logger.SetLogger` versus `logger.Debugf`, and 
attributed the failure to `TestCfgAPI_Export` during the combined run.
   
   ### Reproduction
   
   ```sh
   go test -race -count=10 ./server -run '^(TestCfgAPI_Export|TestCfgAPI_Call)$'
   ```
   
   ### Expected outcome
   
   - Ensure logger initialization and background health-watch lifecycle do not 
race across repeated instance/test lifetimes, addressing the appropriate 
repository if needed.
   - Add or adapt regression coverage and run the two tests together repeatedly 
under `-race`.
   - Once the affected tests are safe in the full suite, remove them from 
`RACE_SKIP_TESTS`.


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