Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: cpu-e2e not work for branch 2.3 #33897

Closed
1 task done
xige-16 opened this issue Jun 17, 2024 · 3 comments
Closed
1 task done

[Bug]: cpu-e2e not work for branch 2.3 #33897

xige-16 opened this issue Jun 17, 2024 · 3 comments
Assignees
@yellow-shine
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@xige-16
Copy link
Contributor

xige-16 commented Jun 17, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.3
- 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

e2e always failed.
https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20HA%20CI/detail/PR-33725/6/pipeline

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@xige-16 xige-16 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 17, 2024
@xige-16
Copy link
Contributor Author

xige-16 commented Jun 17, 2024

@samhuang-z

@yanliang567
Copy link
Contributor

hi @xige-16, thanks for the issues.

/assign @samhuang-z
/unassign

@xige-16
Copy link
Contributor Author

xige-16 commented Jun 17, 2024

link pr:#33725

@xige-16 xige-16 closed this as completed Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yellow-shine yellow-shine

Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xige-16 @yanliang567 @yellow-shine