[Arm] Size-test: Run the binary on CI
Open
Nobody has claimed this yet.
actionable
good first issue
module: arm
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 The feature, motivation and pitch
Today we just build and test for size, but we also want to run it to make sure the build is viable.
Alternatives
No response
Additional context
- CI job - https://github.com/pytorch/executorch/blob/8da2ea6ea98062d73ff5c8da1d9b1ce99ca11a18/.github/workflows/trunk.yml#L220
- We may run into size_test.cpp using FileDataLoader which may not be supported on the baremetal platforms. See arm_executor_runner.cpp for BufferDataLoader use.
RFC (Optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CI job in .github/workflows/trunk.yml around line 220, then inspect size_test.cpp and arm_executor_runner.cpp. Check whether FileDataLoader works on the bare-metal platforms or whether BufferDataLoader is needed. Done means the size-test binary is run in CI and its execution verifies that the Arm build is viable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions
- Domain
- ci-cd, embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100