Webkit builds run unbounded number of jobs and crash your computer
Last week I ended up turning off everything on my machine and setting my builders
to only 1 parallel build in order to churn out a single webkit build, after having my computer mysteriously crash in the middle of webkit builds multiple times a day for two days in a row.
Then I discovered: d5b81831
There must be better ways to do this, and it must be more important that a developer can build on their own computer than it is important for CI to churn out webkit builds quickly.
I think we should start by reverting the brute force approach which causes WebKit to crash computers (it had really never done that to me before this).
I suggest that we increase the limit of 8 parallel jobs per build to something higher for now in BuildStream at _project.py:591.
Note that this limit is imposed already because when it is unbounded, we allocate too many jobs on build servers with a ridiculous number of cores.
The next step would be to add a configuration for max-jobs
in BuildStream, so that users (users include CI configurations here) could control the number of jobs per build in addition to the number of parallel builds possible.
The ultimate solution would be to run a job server that is shared between sandboxed builds, but that is really complicated :)