-
Notifications
You must be signed in to change notification settings - Fork 606
Fix of the test-arm-backend-delegation flow #2143
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
Signed-off-by: Rob Elliott <[email protected]>
…d-delegation and test-arm-reference-delegation to use the per-test setup.sh artefacts. Signed-off-by: Rob Elliott <[email protected]>
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/2143
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 30aa02d with merge base f327e53 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
hi @larryliu0820 - I don't think these llama job failures are due to my changes - more likely from the llama test enabling in #2092 ? edit: I've now merged changes from main so this hopefully reintroduces the new script options for those tests to pass. |
Signed-off-by: Rob Elliott <[email protected]>
Signed-off-by: Rob Elliott <[email protected]>
Signed-off-by: Rob Elliott <[email protected]>
@mergennachin has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@mergennachin merged this pull request in 843db93. |
There are a few oddities in the test setup, hopefully this fixes #2011 and fixes #1947.
Probably fixes #1750 as well.
The change is to use a per-test-run build of the setup.sh / SDK components rather than one in /opt/arm-sdk - the setup.sh inlcudes a pip install of a vela executable into the venv path which was not correctly carried through into the test run.
Once this works we can remove the Docker stage which is running setup.sh