You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... since they are subject to forces outside of version control
use case: being able to bump the EC2 instance type to get more RAM/CPU without breaking all pending PRs because partest runs out of ram in this new environment. We should not have to depend on everyone rebasing on our latest fix to counter-act these changes, so that means that e.g., concurrency and Java heap sizing should be configurable using environment vars?
The text was updated successfully, but these errors were encountered:
For now, I've reverted my desperate change to bump our EC2 instance type as it had these unexpected consequences. We first need to prepare for those with something along the lines of scala/scala#5434 or perhaps more generally hooks in our CI scripts so that we can control them outside of git.
... since they are subject to forces outside of version control
use case: being able to bump the EC2 instance type to get more RAM/CPU without breaking all pending PRs because partest runs out of ram in this new environment. We should not have to depend on everyone rebasing on our latest fix to counter-act these changes, so that means that e.g., concurrency and Java heap sizing should be configurable using environment vars?
The text was updated successfully, but these errors were encountered: