-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Use @pytorch//
in bazel build files
#89660
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/89660
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 FailuresAs of commit cc7bea3: NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I didn't add the |
/easycla |
@vors Could you check that the email on your commits listed in your GitHub account? This seems to be an issue that upsets EasyCLA. |
@kit1980 thank you! I plan to do more contributions as part of my work at Cruise, as well as help my teammates to do the same. Since PyTorch now part of Linux Foundation it seems like CLA also changed? Let me spend a little bit of time sorting out CLA with our legal team. |
@vors besides signing the CLA, there is a technical CLA-check related detail: email on the commit (as seen by git) must be listed in your GitHub account, this seems to be not the case currently. |
Oh I see, let me fix it :) |
Ok I worked with our legal, we signed CLA and I'm now CLA manager for Cruise. This should be ready to merge from the legal point on view :) @kit1980 can you help with the code review? |
/easycla |
@pytorchbot /rebase |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot rebase |
You don't have permissions to rebase this PR, only people with write permissions may rebase PRs. |
@pytorchbot rebase -b master |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
30d64da
to
d1befe9
Compare
This comment was marked as resolved.
This comment was marked as resolved.
/easycla |
d1befe9
to
cc7bea3
Compare
/easycla |
@kit1980 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Gentle ping on this one, can we start getting a review? |
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 2 additional jobs have failed, first few of them are: trunk ,trunk / linux-focal-rocm5.3-py3.8 / test (default, 2, 2, linux.rocm.gpu) Details for Dev Infra teamRaised by workflow job |
Seems unrelated... |
@pytorchbot merge |
@pytorchbot sudo merge |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot merge -f "Pre-existing ROCm issues" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
@kit1980 🙇 |
This is a follow-up from #89660 There is another place that needs to be updated. I think this time I covered all of them... Pull Request resolved: #91424 Approved by: https://github.com/malfet
What are the edge cases under which // resolves to the top-level workspace? |
There are 3 flavors:
From our expirience in Cruise, only the last one provides an unambiguous stable resolution. |
This change aims to make bazel build more embeeding-friendly.
Namely, when PyTorch is included as an external repo in another project, it is usually included like this
Or
In this case, references to
@//
would resolve to the top-level WORKSPACE that includes PyTorch.That makes upgrades harder because we need to carry around this patch.
Note that under some edge-case circumstances even
//
resolves to the top-levelWORKSPACE
.This change makes the embedding of the bazel build easier without compromising anything for the main repo, since the
@pytorch//
still refers to the same thing.cc @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @VitalyFedyunin @jgong5 @mingfeima @sanchitintel @ashokei @jingxu10 @min-jean-cho @yanbing-j @Guobing-Chen @Xia-Weiwen