KEMBAR78
Test shape analysis with opinfos by eellison · Pull Request #59814 · pytorch/pytorch · GitHub
Skip to content

Conversation

@eellison
Copy link
Contributor

@eellison eellison commented Jun 10, 2021

Stack from ghstack:

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if assert_jit_shape_analysis is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: D30200058

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Jun 10, 2021

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 3bdbaf1 (more details on the Dr. CI page):


  • 4/4 failures possibly* introduced in this PR
    • 1/4 non-scanned failure(s)

🕵️ 2 new failures recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

See CircleCI build pytorch_xla_linux_bionic_py3_6_clang9_build (1/2)

Step: "(Optional) Merge target branch" (full log | diagnosis details | 🔁 rerun)

Automatic merge failed; fix conflicts and then commit the result.
CONFLICT (add/add): Merge conflict in torch/csrc/jit/python/init.cpp
Auto-merging torch/csrc/jit/python/init.cpp
CONFLICT (add/add): Merge conflict in torch/csrc/jit/passes/symbolic_shape_analysis.cpp
Auto-merging torch/csrc/jit/passes/symbolic_shape_analysis.cpp
CONFLICT (add/add): Merge conflict in torch/csrc/jit/passes/remove_mutation.cpp
Auto-merging torch/csrc/jit/passes/remove_mutation.cpp
CONFLICT (add/add): Merge conflict in torch/_C/__init__.pyi.in
Auto-merging torch/_C/__init__.pyi.in
CONFLICT (add/add): Merge conflict in test/test_ops.py
Auto-merging test/test_ops.py
Automatic merge failed; fix conflicts and then commit the result.


Exited with code exit status 1

See CircleCI build pytorch_linux_xenial_py3_6_gcc5_4_build (2/2)

Step: "(Optional) Merge target branch" (full log | diagnosis details | 🔁 rerun)

Automatic merge failed; fix conflicts and then commit the result.
CONFLICT (add/add): Merge conflict in torch/csrc/jit/python/init.cpp
Auto-merging torch/csrc/jit/python/init.cpp
CONFLICT (add/add): Merge conflict in torch/csrc/jit/passes/symbolic_shape_analysis.cpp
Auto-merging torch/csrc/jit/passes/symbolic_shape_analysis.cpp
CONFLICT (add/add): Merge conflict in torch/csrc/jit/passes/remove_mutation.cpp
Auto-merging torch/csrc/jit/passes/remove_mutation.cpp
CONFLICT (add/add): Merge conflict in torch/_C/__init__.pyi.in
Auto-merging torch/_C/__init__.pyi.in
CONFLICT (add/add): Merge conflict in test/test_ops.py
Auto-merging test/test_ops.py
Automatic merge failed; fix conflicts and then commit the result.


Exited with code exit status 1


1 failure not recognized by patterns:

Job Step Action
CircleCI pytorch_linux_bionic_cuda10_2_cudnn7_py3_9_gcc7_test2 Set Up CI Environment After attach_workspace 🔁 rerun

ci.pytorch.org: 1 failed


This 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 to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Jun 10, 2021
eellison pushed a commit that referenced this pull request Jun 10, 2021
ghstack-source-id: 106ae52
Pull Request resolved: #59814
@eellison eellison mentioned this pull request Jun 10, 2021
Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃 

[ghstack-poisoned]
Elias Ellison and others added 2 commits July 8, 2021 17:56
Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃 

[ghstack-poisoned]
Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃 

[ghstack-poisoned]
@mruberry
Copy link
Collaborator

OpInfo-related changes look good in this PR but see comments in #59812 about a couple tweaks that should make the changes even simpler

Elias Ellison added 2 commits July 21, 2021 17:18
Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃 

[ghstack-poisoned]
Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃 

[ghstack-poisoned]
eellison pushed a commit that referenced this pull request Aug 9, 2021
ghstack-source-id: 1213d8a
Pull Request resolved: #59814
@eellison eellison requested a review from mruberry August 9, 2021 16:42
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@mruberry there may be changes on the other PR but I think this one is ready to go

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃 

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: [D30200058](https://our.internmc.facebook.com/intern/diff/D30200058)

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: [D30200058](https://our.internmc.facebook.com/intern/diff/D30200058)

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: [D30200058](https://our.internmc.facebook.com/intern/diff/D30200058)

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: [D30200058](https://our.internmc.facebook.com/intern/diff/D30200058)

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: [D30200058](https://our.internmc.facebook.com/intern/diff/D30200058)

[ghstack-poisoned]
eellison pushed a commit that referenced this pull request Aug 9, 2021
ghstack-source-id: 9cf0252
Pull Request resolved: #59814
@eellison
Copy link
Contributor Author

eellison commented Aug 9, 2021

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs 😃

Differential Revision: [D30200058](https://our.internmc.facebook.com/intern/diff/D30200058)

[ghstack-poisoned]
eellison pushed a commit that referenced this pull request Aug 10, 2021
ghstack-source-id: f16f017
Pull Request resolved: #59814
@eellison
Copy link
Contributor Author

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@eellison merged this pull request in ea808df.

@facebook-github-bot facebook-github-bot deleted the gh/eellison/192/head branch August 14, 2021 14:18
alanwaketan pushed a commit that referenced this pull request Aug 17, 2021
Summary:
Pull Request resolved: #59814

Using opinfos to test shape analysis. By default, we just check that we don't give incorrect answers, and then if `assert_jit_shape_analysis` is true, tests that we correctly propagates the full shape. and it found a couple bugs {emoji:1f603}

Test Plan: Imported from OSS

Reviewed By: Krovatkin

Differential Revision: D30200058

Pulled By: eellison

fbshipit-source-id: 6226be87f5390277cfa5a1fffaa1b072d4bc8803
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed Merged oncall: jit Add this issue/PR to JIT oncall triage queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants