-
Notifications
You must be signed in to change notification settings - Fork 741
make ExecuTorch program always has valid debug handle map and delegate map #13149
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13149
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 1 Unrelated FailureAs of commit 5a3e4c1 with merge base 134becb ( NEW FAILURES - The following jobs have failed:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D79706058 |
This PR needs a
|
…e map (pytorch#13149) Summary: Currently ExecuTorchProgram's debug handle map and delegate map will be empty if we didn't call its _get_emitter_output function directly or indrectly before. This behavior doesn't make sense because: a. the empty result can not reflect the executorch program's state b. not in line with ExecuTorchProgramManager behavior c. other attributes, like self.buffer and self.program, do not have such behavir and can always return valid result. This PR makes them always has valid value.. Differential Revision: D79706058
3c1a450 to
30f7c34
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79706058 |
…e map (pytorch#13149) Summary: Pull Request resolved: pytorch#13149 Currently ExecuTorchProgram's debug handle map and delegate map will be empty if we didn't call its _get_emitter_output function directly or indrectly before. This behavior doesn't make sense because: a. the empty result can not reflect the executorch program's state b. not in line with ExecuTorchProgramManager behavior c. other attributes, like self.buffer and self.program, do not have such behavir and can always return valid result. This PR makes them always has valid value.. Differential Revision: D79706058
30f7c34 to
428f603
Compare
…e map (pytorch#13149) Summary: Currently ExecuTorchProgram's debug handle map and delegate map will be empty if we didn't call its _get_emitter_output function directly or indrectly before. This behavior doesn't make sense because: a. the empty result can not reflect the executorch program's state b. not in line with ExecuTorchProgramManager behavior c. other attributes, like self.buffer and self.program, do not have such behavir and can always return valid result. This PR makes them always has valid value.. Differential Revision: D79706058
428f603 to
afbe13b
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79706058 |
…e map (pytorch#13149) Summary: Currently ExecuTorchProgram's debug handle map and delegate map will be empty if we didn't call its _get_emitter_output function directly or indrectly before. This behavior doesn't make sense because: a. the empty result can not reflect the executorch program's state b. not in line with ExecuTorchProgramManager behavior c. other attributes, like self.buffer and self.program, do not have such behavir and can always return valid result. This PR makes them always has valid value.. Differential Revision: D79706058
afbe13b to
7d5ece5
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79706058 |
…e map (pytorch#13149) Summary: Currently ExecuTorchProgram's debug handle map and delegate map will be empty if we didn't call its _get_emitter_output function directly or indrectly before. This behavior doesn't make sense because: a. the empty result can not reflect the executorch program's state b. not in line with ExecuTorchProgramManager behavior c. other attributes, like self.buffer and self.program, do not have such behavir and can always return valid result. This PR makes them always has valid value.. Reviewed By: JacobSzwejbka Differential Revision: D79706058
7d5ece5 to
5a3e4c1
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79706058 |
…e map Differential Revision: D79706058 Pull Request resolved: pytorch#13149
Summary:
Currently ExecuTorchProgram's debug handle map and delegate map will be empty if we didn't call its _get_emitter_output function directly or indrectly before. This behavior doesn't make sense because:
a. the empty result can not reflect the executorch program's state
b. not in line with ExecuTorchProgramManager behavior
c. other attributes, like self.buffer and self.program, do not have such behavir and can always return valid result.
This PR makes them always has valid value..
Differential Revision: D79706058