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>
14 lines
402 B
Bash
14 lines
402 B
Bash
#!/bin/bash
|
|
|
|
set -ex
|
|
|
|
git clone https://gitlab.freedesktop.org/mesa/piglit.git --single-branch --no-checkout /piglit
|
|
pushd /piglit
|
|
git checkout 8771c3860505db2bcf4877216221d774bf90af6b
|
|
patch -p1 <$OLDPWD/.gitlab-ci/piglit/disable-vs_in.diff
|
|
cmake -G Ninja -DCMAKE_BUILD_TYPE=Release
|
|
ninja
|
|
find -name .git -o -name '*ninja*' -o -iname '*cmake*' -o -name '*.[chao]' | xargs rm -rf
|
|
rm -rf target_api
|
|
popd
|