-
Notifications
You must be signed in to change notification settings - Fork 652
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
Separate contrib jobs per instrumentation #3499
Comments
Will this have any negative impact on Github actions quota? IIUC this will run more small jobs which each get queued separately |
Well, aparently the quota is not measured in jobs but in minutes, and since this is simply splitting a long job into smaller ones, I don't think it would increase substantially the amount of minutes considering overhead should be small. The maximum amount of jobs depends on the account type. I'll reach out to the organization managers to check if we can make this change without impacting the organization. |
Every contrib instrumentation is run in the same job, which produces logfiles which are extremely long and hard to debug. Also, if one of the runs fails and we want to run it again, it means running the entire job which is very slow. Separate the instrumentation job into multiple jobs, one per instrumentation.
The text was updated successfully, but these errors were encountered: