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]: GrowingRawData of test groupby failed #34713

Closed
1 task done
zhagnlu opened this issue Jul 16, 2024 · 7 comments
Closed
1 task done

[Bug]: GrowingRawData of test groupby failed #34713

zhagnlu opened this issue Jul 16, 2024 · 7 comments
Assignees
@MrPresent-Han
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@zhagnlu
Copy link
Contributor

zhagnlu commented Jul 16, 2024

Is there an existing issue for this?

  • 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

TEST(GroupBY, GrowingRawData) failed

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@zhagnlu zhagnlu 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 Jul 16, 2024
@zhagnlu
Copy link
Contributor Author

zhagnlu commented Jul 16, 2024

@MrPresent-Han

@zhagnlu
Copy link
Contributor Author

zhagnlu commented Jul 16, 2024

related with: #34586

@MrPresent-Han
Copy link
Contributor

I will handle this

@MrPresent-Han
Copy link
Contributor

/assign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 16, 2024
@yanliang567 yanliang567 removed their assignment Jul 16, 2024
@xiaofan-luan
Copy link
Collaborator

@zhagnlu
what's the reason of this failure?

@MrPresent-Han
Copy link
Contributor

has found the cause, a bug I introduced last week

MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Jul 17, 2024
fix: non-init seg_offset for growing raw-data when doing groupby(milv…
ac6102e 
…us-io#34713)

Signed-off-by: MrPresent-Han <[email protected]>
This was referenced Jul 17, 2024
Merged
Merged
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Jul 18, 2024
fix: non-init seg_offset for growing raw-data when doing groupby(milv…
eb7e3e9 
…us-io#34713)

Signed-off-by: MrPresent-Han <[email protected]>
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Jul 18, 2024
fix: non-init seg_offset for growing raw-data when doing groupby(milv…
3554633 
…us-io#34713)

Signed-off-by: MrPresent-Han <[email protected]>
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Jul 19, 2024
fix: non-init seg_offset for growing raw-data when doing groupby(milv…
942e41a 
…us-io#34713)

Signed-off-by: MrPresent-Han <[email protected]>
sre-ci-robot pushed a commit that referenced this issue Jul 19, 2024
@MrPresent-Han
fix: non-init seg_offset for growing raw-data when doing groupby(#34748…
e11aab3 
…) (#34750)

related: #34713
pr: #34748

Signed-off-by: MrPresent-Han <[email protected]>
Co-authored-by: MrPresent-Han <[email protected]>
sre-ci-robot pushed a commit that referenced this issue Jul 19, 2024
@MrPresent-Han
fix: non-init seg_offset for growing raw-data when doing groupby (#34748
ed057e6 
)

related:  #34713

Signed-off-by: MrPresent-Han <[email protected]>
Co-authored-by: MrPresent-Han <[email protected]>
@stale Stale
Copy link

stale bot commented Aug 18, 2024

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.

@stale stale bot added the stale indicates no udpates for 30 days label Aug 18, 2024
@stale stale bot closed this as completed Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MrPresent-Han MrPresent-Han

Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zhagnlu @yanliang567 @xiaofan-luan @MrPresent-Han