diff options
| author | Eric Anholt <eric@anholt.net> | 2019-11-06 11:14:14 -0800 |
|---|---|---|
| committer | Eric Anholt <eric@anholt.net> | 2019-11-06 11:38:07 -0800 |
| commit | cb655d255466cb2f326ebb8546f37434b5bdb16d (patch) | |
| tree | 680518939bf0ab4d7837700afab6ceb7b6274a04 /.gitlab-ci/meson-build.sh | |
| parent | 94e6d17043e2dab2fb0375cf09c26cf5f35b2d73 (diff) | |
Revert "ci: Switch over to an autoscaling GKE cluster for builds."
This reverts commit c9df92bf795af878c38538c85f781291c78ec513.
It turns out that gitlab-runner uses kubernetes all wrong, spawning Pods
and sshing into them to run the script instead of Jobs containing the
script to run. This means that when anything goes wrong with the pod
(autoscale, preemption, VM maintenance, cluster reconfiguration), the job
fails and only sometimes gets handled as a runner system failure. Even
worse, due to bugs in either the runner or k8s itself, some classes of
timeout-related failure end up not being reported as failures, and the job
will incorrectly report success!
Disable using the "autoscale" cluster until we can do something else
(docker-machine instead of k8s, or the custom third-party k8s-native
runner).
Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
Acked-by: Daniel Stone <daniels@collabora.com>
Diffstat (limited to '.gitlab-ci/meson-build.sh')
| -rwxr-xr-x | .gitlab-ci/meson-build.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab-ci/meson-build.sh b/.gitlab-ci/meson-build.sh index 0f4f490447d..d56e526ef20 100755 --- a/.gitlab-ci/meson-build.sh +++ b/.gitlab-ci/meson-build.sh @@ -58,7 +58,7 @@ meson _build --native-file=native.file \ ${EXTRA_OPTION} cd _build meson configure -ninja ${NINJA_FLAGS} +ninja -j4 LC_ALL=C.UTF-8 ninja test ninja install cd .. |