Eric Anholt c1e7e83d52 ci: Consistently use -j4 across x86 build jobs and -j8 on ARM. ... 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>		2020-04-01 18:33:58 +00:00
..
arm_build.sh	ci: Consistently use -j4 across x86 build jobs and -j8 on ARM.	2020-04-01 18:33:58 +00:00
arm_test.sh	ci: Enable ccache in the container builds.	2020-03-17 10:44:39 -07:00
container_post_build.sh	ci: Enable ccache in the container builds.	2020-03-17 10:44:39 -07:00
container_pre_build.sh	ci: Consistently use -j4 across x86 build jobs and -j8 on ARM.	2020-04-01 18:33:58 +00:00
lava_arm.sh	ci: Consistently use -j4 across x86 build jobs and -j8 on ARM.	2020-04-01 18:33:58 +00:00
llvm-snapshot.gpg.key	gitlab-ci: Test against LLVM / clang 9 on x86	2020-01-07 11:00:16 +01:00
x86_build.sh	ci: Consistently use -j4 across x86 build jobs and -j8 on ARM.	2020-04-01 18:33:58 +00:00
x86_build_old.sh	ci: Enable ccache in the container builds.	2020-03-17 10:44:39 -07:00
x86_test-gl.sh	ci: Enable ccache in the container builds.	2020-03-17 10:44:39 -07:00
x86_test-vk.sh	gitlab-ci: add Wine, win64's apitrace and DXVK to the Vulkan testing container	2020-03-27 13:48:17 +00:00