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

   ### ✅ 验证清单
   
   - [x] 🔍 我已经搜索过 [现有 
Issues](https://github.com/apache/dubbo-go/issues),确信这不是重复问题
   
   ### 🚀 Go 版本
   
   1.24+
   
   ### 📦 Dubbo-go 版本
   
   3.3.1
   
   ### 🖥️ 服务端配置
   
   _No response_
   
   ### 💻 客户端配置
   
   _No response_
   
   ### 🌐 协议配置
   
   _No response_
   
   ### 📋 注册中心配置
   
   _No response_
   
   ### 💾 操作系统
   
   🪟 Windows
   
   ### 📝 Bug 描述
   
    ## What happened
   The test 
`Test_multiplyConditionRoute_route/test_multiply_destination_with_ignore_some_condition`
 in `cluster/router/condition/router_test.go` is flaky and fails intermittently 
in CI.
   
https://github.com/apache/dubbo-go/actions/runs/21290486533/job/61282574758?pr=3175
   ##  Error message
   --- FAIL: Test_multiplyConditionRoute_route (0.57s)
       --- FAIL: 
Test_multiplyConditionRoute_route/test_multiply_destination_with_ignore_some_condition
 (0.21s)
           router_test.go:1374: 
               Error Trace:    cluster/router/condition/router_test.go:1374
               Error:          out of range
   
   
   ### Related log:
   ERROR condition/dynamic_router.go:86 
requestconsumer://:/com.foo.BarService?env=gray&region=beijing 
         route an empty set in condition-route:: 
request=env=gray,invokers!=env=ErrTag
   
   ### 🔄 重现步骤
   
   CI environment: GitHub Actions
   
   This flaky test was observed in PR #3175, which only modifies 
filter/generic/ and is completely unrelated to cluster/router/condition/.
   
   ### ✅ 预期行为
   
   ci 通过
   
   ### ❌ 实际行为
   
    ci 没通过
   
   ### 💡 可能的解决方案
   
   _No response_


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