[Bug]: ut coredump occasionally because of floating exception

[zhagnlu]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

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

Current Behavior

73Z ] 2024-07-04T05:01:13.7586992Z ] => failed to load row ID or timestamp, potential missing bin logs or empty segments. Segment ID = -1 2024-07-04T05:01:13.7598938Z [ OK ] Sealed.ClearData (5538 ms) 2024-07-04T05:01:13.7599447Z [ RUN ] Sealed.LoadFieldDataMmap 2024-07-04T05:01:19.2557907Z => failed to load row ID or timestamp, potential missing bin logs or empty segments. Segment ID = -1 2024-07-04T05:01:19.4390800Z ./scripts/run_cpp_codecov.sh: line 65: 217 Floating point exception(core dumped) ${MILVUS_CORE_UNITTEST_DIR}/${test} 2024-07-04T05:01:19.4391709Z 2024-07-04T05:01:19.4392564Z /go/src/github.com/milvus-io/milvus/internal/core/output/unittest/all_tests run failed 2024-07-04T05:01:19.6235667Z ##[error]Process completed with exit code 255. 2024-07-04T05:01:19.6327134Z Post job cleanup.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @zhagnlu /unassign

[stale[bot]]

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.