search

milvus-io / milvus

A cloud-native vector database, storage for next generation AI applications
https://milvus.io
Apache License 2.0
29.37k stars 2.82k forks source link

[Bug]: Unittest `TestSimulation/TestDispatchToVchannels` is not stable #35150

Closed congqixia closed 4 days ago

congqixia commented 1 month ago

Is there an existing issue for this?

Environment

- Milvus version: a9744d6
- Deployment mode(standalone or cluster): n/a
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Unittest TestSimulation/TestDispatchToVchannels is not stable

Expected Behavior

unit test shall pass stably

Steps To Reproduce

No response

Milvus Log

     manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
[2024/07/31 09:08:13.665 +00:00] [DEBUG] [config/refresher.go:71] ["etcd refreshConfigurations"] [prefix=by-dev/config] [endpoints="[etcd:2379]"]
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels
    manager_test.go:317: 
            Error Trace:    /go/src/github.com/milvus-io/milvus/pkg/mq/msgdispatcher/manager_test.go:317
            Error:          Not equal: 
                            expected: 53
                            actual  : 0
            Test:           TestSimulation/TestDispatchToVchannels

Anything else?

No response

congqixia commented 1 month ago

https://github.com/milvus-io/milvus/actions/runs/10175669319/job/28145655395

XuanYang-cn commented 1 month ago

https://github.com/milvus-io/milvus/actions/runs/10161576114/job/28101749059?pr=35100

stale[bot] commented 1 week ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.