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]: building failed under osx #38434

Open
1 task done
tedxu opened this issue Dec 13, 2024 · 1 comment
Open
1 task done

[Bug]: building failed under osx #38434

tedxu opened this issue Dec 13, 2024 · 1 comment
Assignees
@tedxu
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tedxu
Copy link
Contributor

tedxu commented Dec 13, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

There are multiple build failures and tool chain breaks under OSX.

  1. If build make test-cpp, there is build failure reporting use of undclared identifier 'MAP_ANON'
  2. If format with clang-format, there is error reporting grep: repetition-operator operand invalid

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@tedxu tedxu 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 Dec 13, 2024
This was referenced Dec 13, 2024
Open
Merged
sre-ci-robot pushed a commit that referenced this issue Dec 13, 2024
@tedxu
fix: UT compile broken under osx (#38432)
3038383 
See: #38434

---------

Signed-off-by: Ted Xu <[email protected]>
@yanliang567
Copy link
Contributor

/assign @tedxu
/unassign

@sre-ci-robot sre-ci-robot assigned tedxu and unassigned yanliang567 Dec 13, 2024
@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 Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tedxu tedxu

Labels
kind/bug Issues or changes related a bug 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
2 participants
@tedxu @yanliang567