Skip to content

Revert "[quant][graphmode] Skip quantizing input and output in matched module (#32814)"#34188

Closed
ljk53 wants to merge 1 commit intogh/ljk53/114/basefrom
gh/ljk53/114/head
Closed

Revert "[quant][graphmode] Skip quantizing input and output in matched module (#32814)"#34188
ljk53 wants to merge 1 commit intogh/ljk53/114/basefrom
gh/ljk53/114/head

Conversation

@ljk53
Copy link
Copy Markdown
Contributor

@ljk53 ljk53 commented Mar 4, 2020 •
edited
Loading

@ljk53
Revert "[quant][graphmode] Skip quantizing input and output in matche…
278da51 
…d module (#32814)"

This reverts commit e5bbd23.

[ghstack-poisoned]
@ljk53 ljk53 requested a review from apaszke as a code owner March 4, 2020 06:11
ljk53 added a commit that referenced this pull request Mar 4, 2020
@ljk53
Revert "[quant][graphmode] Skip quantizing input and output in matche…
243a3cd 
…d module (#32814)"

This reverts commit e5bbd23.

ghstack-source-id: 19a0174
Pull Request resolved: #34188
@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Mar 4, 2020
@dr-ci
Copy link
Copy Markdown

dr-ci Bot commented Mar 4, 2020 •
edited
Loading

💊 CircleCI build failures summary and remediations

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

✅ None of the build failures appear to be your fault 💚

  • 2/9 tentatively recognized as flaky ❄️

  • 7/9 broken upstream at merge base 2ba74b7 since Mar 04

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

    If your commit is newer than viable/strict, you can try basing on an older, stable commit:

    git fetch origin viable/strict
git rebase --onto viable/strict $(git merge-base origin/master HEAD)

    If your commit is older than viable/strict:

    git fetch origin viable/strict
git rebase viable/strict

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

❄️ 2 tentatively flaky failures

2 failures tentatively classified as flaky but have not launched reruns to confirm:

See CircleCI build pytorch_linux_xenial_py3_6_gcc5_4_test (1/2)

Step: "Test" (full log | pattern match details) ❄️

Mar 04 07:11:25 RuntimeError: Error downloading resource! 
Mar 04 07:11:25  
Mar 04 07:11:25 During handling of the above exception, another exception occurred: 
Mar 04 07:11:25  
Mar 04 07:11:25 Traceback (most recent call last): 
Mar 04 07:11:25   File "tools/download_mnist.py", line 87, in <module> 
Mar 04 07:11:25     main() 
Mar 04 07:11:25   File "tools/download_mnist.py", line 80, in main 
Mar 04 07:11:25     download(path, url, options.quiet) 
Mar 04 07:11:25   File "tools/download_mnist.py", line 41, in download 
Mar 04 07:11:25     raise RuntimeError('Error downloading resource!') 
Mar 04 07:11:25 RuntimeError: Error downloading resource! 
Mar 04 07:11:25 + cleanup 
Mar 04 07:11:25 + retcode=1 
Mar 04 07:11:25 + set +x 
Mar 04 07:11:25 =================== sccache compilation log =================== 
Mar 04 07:11:25 ERROR:sccache::server: Compilation failed: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "/tmp/torch_extensions/test_compilation_error_formatting/main.cpp: In function \'int main()\':\n/tmp/torch_extensions/test_compilation_error_formatting/main.cpp:2:23: error: expected \';\' before \'}\' token\n int main() { return 0 }\n                       ^\n" } 
Mar 04 07:11:25  
Mar 04 07:11:25 =========== If your build fails, please take a look at the log above for possible reasons =========== 
Mar 04 07:11:25 Compile requests                 68 
Mar 04 07:11:25 Compile requests executed        28 
Mar 04 07:11:25 Cache hits                       21

See CircleCI build pytorch_linux_xenial_cuda10_1_cudnn7_py3_slow_test (2/2)

Step: "Test" (full log | pattern match details) ❄️

Mar 04 08:26:50 RuntimeError: Error downloading resource! 
Mar 04 08:26:50  
Mar 04 08:26:50 During handling of the above exception, another exception occurred: 
Mar 04 08:26:50  
Mar 04 08:26:50 Traceback (most recent call last): 
Mar 04 08:26:50   File "tools/download_mnist.py", line 87, in <module> 
Mar 04 08:26:50     main() 
Mar 04 08:26:50   File "tools/download_mnist.py", line 80, in main 
Mar 04 08:26:50     download(path, url, options.quiet) 
Mar 04 08:26:50   File "tools/download_mnist.py", line 41, in download 
Mar 04 08:26:50     raise RuntimeError('Error downloading resource!') 
Mar 04 08:26:50 RuntimeError: Error downloading resource! 
Mar 04 08:26:50 + cleanup 
Mar 04 08:26:50 + retcode=1 
Mar 04 08:26:50 + set +x 
Mar 04 08:26:50 =================== sccache compilation log =================== 
Mar 04 08:26:50 ERROR:sccache::server: Compilation failed: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "/tmp/torch_extensions/test_compilation_error_formatting/main.cpp: In function \'int main()\':\n/tmp/torch_extensions/test_compilation_error_formatting/main.cpp:2:23: error: expected \';\' before \'}\' token\n int main() { return 0 }\n                       ^\n" } 
Mar 04 08:26:50  
Mar 04 08:26:50 =========== If your build fails, please take a look at the log above for possible reasons =========== 
Mar 04 08:26:50 Compile requests                161 
Mar 04 08:26:50 Compile requests executed        57 
Mar 04 08:26:50 Cache hits                       10

🚧 7 upstream failures recognized by patterns:

These were probably caused by upstream breakages:

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.

This comment has been revised 5 times.

@ljk53 ljk53 mentioned this pull request Mar 4, 2020
Closed
@ljk53 ljk53 closed this Mar 5, 2020
@facebook-github-bot facebook-github-bot deleted the gh/ljk53/114/head branch April 4, 2020 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@apaszke apaszke Awaiting requested review from apaszke

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ljk53 @facebook-github-bot