[reland] Process inputs and outputs in fx interpreter

[842974287]

Summary: Forgot to update the expect file in #74242. Reland to include changes in expect file.

Test Plan: unit test

Differential Revision: D35089989

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/74637
• ↩️  [fb-only] Re-run with SSH instructions
• Need help or want to give feedback on the CI? Visit our office hours

💊 CI failures summary and remediations

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

---

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

---

• 1/1 broken upstream at merge base 85d8647 on Mar 23 from 2:42pm to 4:31pm

---

🚧 1 fixed upstream failure:

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

• pull / pytorch-xla-linux-bionic-py3.7-clang8 / test (xla, 1, 1, linux.2xlarge) on Mar 23 from 2:42pm to 4:31pm (f7ee308 - d583f9c)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D35089989

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D35089989

[github-actions]

Hey @842974287.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.