-
Notifications
You must be signed in to change notification settings - Fork 315
OSS edenfs_linux build fixes #1101
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.
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
base: main
Are you sure you want to change the base?
Conversation
…brary dependencies Summary: Fixes integration test failure due to lack of a functioning python-psutil (on Linux, this requires the inclusion of native code which is not permitted in a zipapp). Test Plan: Run the following: ``` act --container-architecture linux/x86_64 -W ".github/workflows/edenfs_linux.yml" ``` Before this change, integration tests fail with a failure to initialize python-psutil. After this change, integraion tests run cleanly
Summary: Fixes integration test failure due to lack of a functioning python-psutil (on Linux, this requires the inclusion of native code which is not permitted in a zipapp). Test Plan: Run the following: ``` act --container-architecture linux/x86_64 -W ".github/workflows/edenfs_linux.yml" ``` Before this change, integration tests fail with a failure to initialize python-psutil. After this change, integraion tests run cleanly
Summary: Test Plan:
Summary: Test Plan:
Summary: Test Plan:
Summary: TakeoverData is failing to compile in the OSS build Test Plan: Confirm the following gets past the compilation step of TakeoverData.cpp ``` act --container-architecture linux/x86_64 -W ".github/workflows/edenfs_linux.yml" ```
Summary: Test Plan:
@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this in D77674652. (Because this pull request was imported automatically, there will not be any future comments.) |
@ben-- Could you help rebasing this change? I made some changes to satisfy the linters and got some conflicts rebasing this diff - It'd be easier if ShipIt can import a stack as a stack instead of one commit... unfortunately we don't have the right tooling right now. We use |
This change should be landed after or instead of #1100 (it includes that as the first commit)
This PR fixes a number of build issues in the OSS build. Each individual fix can be verified by running:
on the prior commit. (Though, due to job prioritization, sometimes you may find a different issue first.)
The above build still does not complete due to a lack of thrift file generation, but that modification will be largely independent of this "stack".