Skip to content
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

[ONNX] Improve lower tuples and handle control flow (#57650) #58579

Closed
wants to merge 1 commit into from

Conversation

BowenBao
Copy link
Collaborator

@BowenBao BowenBao commented May 19, 2021

Stack from ghstack:

Improving the logic for finding tuple patterns within control flow.
Also fixes: #56914

Co-authored-by: neginraoof neginmr@utexas.edu

Improving the logic for finding tuple patterns within control flow.
Also fixes: #56914

Co-authored-by: neginraoof <neginmr@utexas.edu>

[ghstack-poisoned]
@facebook-github-bot facebook-github-bot added oncall: jit Add this issue/PR to JIT oncall triage queue cla signed labels May 19, 2021
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented May 19, 2021

💊 CI failures summary and remediations

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


  • 1/3 failures introduced in this PR
  • 2/3 broken upstream at merge base ab07251 on May 19 from 8:24am to 2:23pm

🕵️ 1 new failure recognized by patterns

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

See GitHub Actions build Linux CI (pytorch-linux-xenial-py3.6-gcc5.4) / test (1/1)

Step: "Test PyTorch" (full log | diagnosis details | 🔁 rerun)

2021-05-19T20:10:40.3637190Z Build left local git repository checkout dirty
2021-05-19T20:10:34.5105037Z real	73m2.186s
2021-05-19T20:10:34.5105644Z user	127m23.442s
2021-05-19T20:10:34.5105915Z sys	27m20.495s
2021-05-19T20:10:34.5106223Z + assert_git_not_dirty
2021-05-19T20:10:34.5107278Z + [[ pytorch-linux-xenial-py3.6-gcc5.4 != *rocm* ]]
2021-05-19T20:10:34.5108454Z + [[ pytorch-linux-xenial-py3.6-gcc5.4 != *xla* ]]
2021-05-19T20:10:34.5109352Z ++ git status --porcelain
2021-05-19T20:10:40.3635095Z + git_status=' M third_party/tensorpipe'
2021-05-19T20:10:40.3635784Z + [[ -n  M third_party/tensorpipe ]]
2021-05-19T20:10:40.3636590Z + echo 'Build left local git repository checkout dirty'
2021-05-19T20:10:40.3637190Z Build left local git repository checkout dirty
2021-05-19T20:10:40.3637747Z + echo 'git status --porcelain:'
2021-05-19T20:10:40.3638197Z git status --porcelain:
2021-05-19T20:10:40.3638682Z + echo ' M third_party/tensorpipe'
2021-05-19T20:10:40.3639092Z  M third_party/tensorpipe
2021-05-19T20:10:40.3639408Z + exit 1
2021-05-19T20:10:40.3639682Z + cleanup
2021-05-19T20:10:40.3639954Z + retcode=1
2021-05-19T20:10:40.3640237Z + set +x
2021-05-19T20:10:40.3640580Z =================== sccache compilation log ===================
2021-05-19T20:10:40.3829258Z =========== If your build fails, please take a look at the log above for possible reasons ===========

🚧 2 fixed upstream failures:

These were probably caused by upstream breakages that were already fixed.

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

If your commit is older than viable/strict, run these commands:

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla signed oncall: jit Add this issue/PR to JIT oncall triage queue open source
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants