c1e7e83d52
Our shared runners are set up for concurrent jobs ~= CPUs / 4 (x86) or 8 (ARM). If you use more build processes than that, then jobs may be fighting each other for shared system resources, possibly to the point of failure (we've seen one of the runners OOM on some jobs before, though I'm not sure if this was the cause). To try to systematically prevent the problem, we make a ninja wrapper in the containers that passes the -j flags, and set MAKEFLAGS in the container builds. This doesn't cover make in non-container builds, but I believe we don't have any of those. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3782> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3782>
15 lines
285 B
Bash
15 lines
285 B
Bash
#!/bin/bash
|
|
|
|
set -ex
|
|
|
|
git clone https://github.com/ValveSoftware/Fossilize.git
|
|
cd Fossilize
|
|
git checkout 6b5b570008c9ab5269e341f04c811fe49a1bb72c
|
|
git submodule update --init
|
|
mkdir build
|
|
cd build
|
|
cmake .. -DCMAKE_BUILD_TYPE=Release -G Ninja
|
|
ninja -C . install
|
|
cd ../..
|
|
rm -rf Fossilize
|