-
Notifications
You must be signed in to change notification settings - Fork 26.3k
ci: Bump linux runner availability to 750 #75234
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
Was noticing longer than average queuing times for linux.2xlarge and also found out that we're hitting our max limit more often than not so bumping this to 750 to give us more capacity to play around with. Signed-off-by: Eli Uriegas <eliuriegas@fb.com>
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit e5ca583 (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
|
@pytorchbot merge this |
|
Merge failed due to Refusing to merge as mandatory check Lint failed for rule OSS CI |
|
@pytorchbot merge this |
|
Hey @seemethere. |
Summary: Was noticing longer than average queuing times for linux.2xlarge and also found out that we're hitting our max limit more often than not so bumping this to 750 to give us more capacity to play around with. Signed-off-by: Eli Uriegas <eliuriegas@fb.com> <details> <summary> Number of times we've hit this in the last week </summary>  Query: https://fburl.com/6cst46y0 </summary> Pull Request resolved: #75234 Approved by: https://github.com/kit1980, https://github.com/osalpekar, https://github.com/malfet Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/b0e047b59da4d6434bf347dd6ae501169218bb1a Reviewed By: b0noI Differential Revision: D35404320 Pulled By: seemethere fbshipit-source-id: f74d6ec836fad9c2c26eb2b512766f16f29a2c9e
Was noticing longer than average queuing times for linux.2xlarge and
also found out that we're hitting our max limit more often than not so
bumping this to 750 to give us more capacity to play around with.
Signed-off-by: Eli Uriegas eliuriegas@fb.com
Number of times we've hit this in the last week
Query: https://fburl.com/6cst46y0