- 
                Notifications
    You must be signed in to change notification settings 
- Fork 25.7k
split up community documentation, add build/test document #38629
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
        
          
                docs/source/index.rst
              
                Outdated
          
        
      There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
along the way, fix this documentation problem. rpc/index.rst does not exist
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rpc.rst document still exists, and has links to the rpc/*.rst documents.
| 💊 CI failures summary and remediationsAs of commit 493dc24 (more details on the Dr. CI page): 
 ci.pytorch.org: 1 failedThis comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group. This comment has been revised 8 times. | 
| The test failure is unrelated:  | 
| All the top-level *.md pages in the repo should be  | 
| @mattip the changes here look good, but there's nothing in this PR related to  | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, this was to relate to "document how to regenerate the ONNX expect results". A bit much for 4 lines, but I couldn't resist.
        
          
                docs/source/community/testing.rst
              
                Outdated
          
        
      There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the documentation reformatting was to get to this: how to regenerate ONNX test results
| You should probably edit the PR description here, and make the actual ONNX test changes in a separate PR. | 
Summary: closes gh-32561 closes gh-38545. As part of the fallout from gh-36797, this PR - replaces the producer_version: "1.6" in onnx expect tests with `producer_version: "XXX" - adapts `testing/_internal/common_utils.py` with a regex to change the onnx producer_version so tests still pass The consistency of the torch version and the onnx `producer_version` is tested in gh-36797, so there is no reason to test it again in the expect tests. xref gh-38629 which documented how to run the onnx tests and at the same time refactored the Community documentation. Pull Request resolved: #39002 Differential Revision: D21723062 Pulled By: ezyang fbshipit-source-id: 1bd6a8ed37d5383e69d017226dc09c0645a69aff
| ping @jlin27 | 
        
          
                docs/source/index.rst
              
                Outdated
          
        
      There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: kurtamohler <kmohler@quansight.com>
| Rebased to clear conflict caused by http -> https transition. | 
| Hi @mattip! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but we do not have a signature on file. In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! | 
| Closing, too low priority to continue. | 
As part of the fallout from gh-36797, this PR
replaces theproducer_version: "1.6"in expect tests with `producer_version: "XXX"adaptstesting/internal/common_utils.pywith a regex to change the onnxproducer_versionso tests still passtesting.rstto start to explain how to build and test pytorch locallyEXPECTTEST_ACCEPT=1optionEdit: split out the first two items to gh-39002