-
Notifications
You must be signed in to change notification settings - Fork 697
Fix MobileBert timeout CI failures #1729
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/1729
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 658f5fc with merge base 394e15b ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@huydhn has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
| submodules: 'true' | ||
| repository: pytorch/executorch | ||
| upload-artifact: docs | ||
| timeout: 90 |
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.
Not related to MobileBert, but this timeout hasn't been set yet, so doc jobs timeout sometimes after 30m, i.e. https://github.com/pytorch/executorch/actions/runs/7663108516/job/20885389022?pr=1658. Setting it to 90m like the rest of CI jobs.
|
@huydhn has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
I'm making the timeout value configurable for each models and defaults to 90m (the current value). The timeout value for MobileBert can then be increased to
120m180m. The model is running only trunk anyway, so there is no impact on PR duration. A better fix would be to figure out why it's running slowly, but I leave it to the experts.I'm trying to get lint and pull signals all green before landing #1697 (although they are not that related).