-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
CI Paused Until November 24th, 2023 #1398
Comments
Out of interest, can you mention why standard (and free) github runners not suitable and what requires us to use custom ones? |
It boils down to performance and disk usage. The free runners don’t have enough cores to finish our CI jobs in a reasonable time (they already take around 30 minutes per) and the free runners don’t have enough storage space to handle the intermediate artifacts. We’ve spent countless hours getting the jobs to a tolerable level and it’s now cheaper to throw money at it. |
@orf The default runners have sufficiently small disk space that they require hacks like clearing the entire target directory midway to clean out intermediates in order to complete our CI test run. Failure to do so, if we are generating sufficient intermediates, does not fail gracefully: it falls over wailing pathetically on whatever test put it over the disk limit. And it does not explain what happened. It just is a series of bizarre and opaque errors. As we have, in general, insufficient testing, having a situation where, randomly, we are punished for adding tests, is not acceptable. |
Now and then we spot an optimization that reduces our disk usage, and of course we take it:
...but these often don't significantly help the people using pgrx to build software that does stuff. Of course, if someone put quite a lot of time in, they could improve it, and a few of those would translate a little. Then we could, in a situation like this, endure slower iteration cycles rather than simply shrugging and deferring running CI for a week. But if I had to wait the almost-hour the pgrx CI used to take, for every iteration, I would simply not have bothered to solve certain problems, like e.g. |
We blew our CI budget already this month, so CI is paused until the next billing cycle... November 24th, 2023. Enjoy a week off over the US Thanksgiving holiday!
Also, now would be a good time to contact the pgcentral foundation about joining!
The text was updated successfully, but these errors were encountered: