Skip to content

[quant][graphmode] Move numerics changing passes before finalize #37514

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

Closed
wants to merge 9 commits into from

Conversation

jerryzh168
Copy link
Contributor

@jerryzh168 jerryzh168 commented Apr 29, 2020

Stack from ghstack:

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

Differential Revision: D21364008

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
@dr-ci
Copy link

dr-ci bot commented Apr 29, 2020

💊 Build failures summary and remediations

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


None of the build failures appear to be your fault 💚


  • 1/1 broken upstream at merge base e98ad6c on Apr 30 from 2:26pm to 7:04pm PDT (9 commits; cd48fb5 - bedc50e)

    Please rebase on the viable/strict branch (expand for instructions)

    Since your merge base is older than viable/strict, run these commands:

    git fetch https://github.com/pytorch/pytorch viable/strict
    git rebase FETCH_HEAD
    

    Check out the recency history of this "viable master" tracking branch.


1 job timed out:

  • pytorch_xla_linux_bionic_py3_6_clang9_test

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 on the GitHub issue tracker.

See how this bot performed.

This comment has been revised 33 times.

…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
@@ -1133,7 +1107,6 @@ def forward(self, x):
model = torch.jit.script(M()).eval()
model = quantize_script(model, qconfig_dict, _test_only_eval_fn, [data], inplace=False, debug=True)
FileCheck().check_not("quantized::conv2d") \
.check("CallMethod") \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we not check for CallMethod anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, we'll inline the graph in convert so CallMethod from sub module is gone

row->elements().at(0).toStringRef());
row->elements().at(0).toStringRef() == "operators",
"Expected operators but found ",
row->elements().at(0).toStringRef());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this change be here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is clang format changes, got this when I run clang-format-all.py

…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
@jerryzh168 jerryzh168 requested a review from supriyar April 30, 2020 18:51
…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
…nalize"

Summary:
This is to constrain all numerics changing operations in insert quant dequant pass

Test Plan:
python test/test_quantization.py TestQuantizeScriptJitPasses

Reviewers:
.

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
@jerryzh168 jerryzh168 requested a review from raghuramank100 May 1, 2020 01:34
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 5e0a24f.

@facebook-github-bot facebook-github-bot deleted the gh/jerryzh168/294/head branch May 5, 2020 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

5 participants