-
Notifications
You must be signed in to change notification settings - Fork 713
Fix Hard Fault in arm_executor_runner #5302
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
The introduction of the PlatformMemoryAllocator in pytorch#5121 introduced a hard fault in arm_executor_runner when not supplying the temp_allocator in the MemoryManager, so add it to get tests running again. Signed-off-by: Per Åstrand <per.astrand@arm.com> Change-Id: I357244a15c1b1fdee567ad828e09e3607e43e2e7
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/5302
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 0c9d78b with merge base 623b7b6 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
|
||
| torch::executor::MemoryManager memory_manager( | ||
| &method_allocator, &planned_memory); | ||
| &method_allocator, &planned_memory, &temp_allocator); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@manuelcandales shouldn't we fall back to using method allocator if null?
digantdesai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stamping to unbreak CI
|
@digantdesai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@digantdesai merged this pull request in c032194. |
The introduction of the PlatformMemoryAllocator in #5121 introduced a hard fault in arm_executor_runner when not supplying the temp_allocator in the MemoryManager, so add it to get tests running again.
Change-Id: I357244a15c1b1fdee567ad828e09e3607e43e2e7