-
Notifications
You must be signed in to change notification settings - Fork 323
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
Properly kill the buck2 daemon #5373
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/5373
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit f278a60 with merge base a91eb8a (): BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@dbort has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Didn't fix it. https://github.com/pytorch/executorch/actions/runs/10858643573/job/30136900450?pr=5373#step:9:651
|
Fix the `buck2 kill` command. Because of scoping issues, in some cases we only ran "` kill`" because the local value of `$BUCK2` was empty. This should help avoid failures like ``` Error validating working directory Caused by: 0: Failed to stat `/home/ubuntu/cmodi/executorch/buck-out/v2` 1: ENOENT: No such file or directory ``` which are typically fixed by running `buck2 kill`. Add "COMMAND_ECHO" to the kill command to show what we're running. Also, make the function consistently use `executorch_root` as the working directory. We should always run buck2 from the ET repo. Test Plan: ``` rm -rf buck-out (rm -rf cmake-out \ && mkdir cmake-out \ && cd cmake-out \ && cmake ..) ``` Output showed that the local variable works: ``` -- Resolved buck2 as /Users/***/local/executorch/cmake-out/buck2-bin/buck2-99773fe6f7963a72ae5f7b737c02836e. 'mkdir -p '/Users/***/local/executorch/buck-out/v2'' -- Killing buck2 daemon '/Users/***/local/executorch/cmake-out/buck2-bin/buck2-99773fe6f7963a72ae5f7b737c02836e kill' ``` And that the parent variable still works: ``` -- ******** Summary ******** ... -- BUCK2 : /Users/***/local/executorch/cmake-out/buck2-bin/buck2-99773fe6f7963a72ae5f7b737c02836e ```
Reducing the scope of this PR to fix the |
@dbort has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@pytorchbot cherry-pick --onto release/0.4 -c critical |
Fix the
buck2 kill
command. Because of scoping issues, in some cases we only ran "kill
" because the local value of$BUCK2
was empty.This should help avoid failures like
which are typically fixed by running
buck2 kill
.Add "COMMAND_ECHO" to the kill command to show what we're running.
Also, make the function consistently use
executorch_root
as the working directory. We should always run buck2 from the ET repo.Test Plan:
Output showed that the local variable works:
And that the parent variable still works: