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

[FEATURE]Print error log when run coverage.sh #446

Closed
fishpenguin opened this issue Nov 21, 2019 · 1 comment
Closed

[FEATURE]Print error log when run coverage.sh #446

fishpenguin opened this issue Nov 21, 2019 · 1 comment
Labels
good first issue Good for newcomers
Projects
Backlog

Comments

@fishpenguin
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently we only print debug log while running coverage.sh, it's difficult for us to figure out where the problem is when coverage.sh failed.

Describe the solution you'd like
Look how debug log is printed, using the same way to print error log

Describe alternatives you've considered
NA

Additional context
NA
@fishpenguin fishpenguin added the good first issue Good for newcomers label Nov 21, 2019
@jeffoverflow jeffoverflow marked this as a duplicate and then as not a duplicate of #427 Nov 21, 2019
@JinHai-CN
Copy link
Contributor

Duplicate

@JinHai-CN JinHai-CN added this to To do in Backlog via automation Mar 1, 2020
@JinHai-CN JinHai-CN moved this from To do to Review in progress in Backlog Jun 29, 2020
@JinHai-CN JinHai-CN moved this from Review in progress to Reviewer approved in Backlog Jun 29, 2020
@JinHai-CN JinHai-CN moved this from Reviewer approved to Done in Backlog Jun 29, 2020
yah01 pushed a commit to yah01/milvus that referenced this issue Feb 13, 2023
@eddyxu
Take record by Row ID (milvus-io#446)
5f022b8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
No open projects
Backlog
  
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JinHai-CN @fishpenguin