-
Notifications
You must be signed in to change notification settings - Fork 25.6k
update README.md to reflect current build from source status on master #92729
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/92729
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit ae8a1ed: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
4fc79c4
to
18a1ce6
Compare
@pytorchbot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Signed-off-by: Mike Brown <brownwm@us.ibm.com>
Successfully rebased |
18a1ce6
to
ae8a1ed
Compare
@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 |
Signed-off-by: Mike Brown brownwm@us.ibm.com
To avoid new contributor issues when building master a couple README.md comments will help... This change:
- Documents the current support restriction to apt package(fixed now)g++-9
#91328 ** noting here that with the commit in #92911 g++-11.3 appears to build and run local tests at least as well as g++9, so this restriction may be overcome with that PR merge depending on success and CI updates.