-
Notifications
You must be signed in to change notification settings - Fork 683
fix test-huggingface-transformers-* tests #14752
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/14752
Note: Links to docs will display an error until the docs builds have been completed. ❌ 4 New Failures, 1 Unrelated FailureAs of commit cd1c768 with merge base 4372a14 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
@pytorchbot cherry-pick --onto release/1.0 -c regression |
Fix these tests https://hud.pytorch.org/hud/pytorch/executorch/main/1?per_page=50&name_filter=huggingface-transformer The optimum is installed in a bit weird way, inside executorch folder, it clone optimum inside executorch, and try to install executorch in the nested optimum folder. Install optimum via pip instead in the same commit. The behavior should be the same, tests still run as expected (cherry picked from commit 3d8b8d1)
Cherry picking #14752The cherry pick PR is at #14812 and it is recommended to link a regression cherry pick PR with an issue. The following tracker issues are updated: Details for Dev Infra teamRaised by workflow job |
Fix these tests https://hud.pytorch.org/hud/pytorch/executorch/main/1?per_page=50&name_filter=huggingface-transformer
The optimum is installed in a bit weird way, inside executorch folder, it clone optimum inside executorch, and try to install executorch in the nested optimum folder. Install optimum via pip instead in the same commit. The behavior should be the same, tests still run as expected