NetworkManager/.gitlab-ci
Thomas Haller 01730f5943
gitlab-ci: set OMP_NUM_THREADS=1 to avoid libgomp crash for msgmerge
It's not clear why this happens. But since recently in our gitlab-ci,
all the Fedora machines will fail. It happens in the step

  check_run_clean 6 && test $IS_FEDORA = 1 -o $IS_CENTOS = 1 && ./contrib/fedora/rpm/build_clean.sh -g -w crypto_gnutls -w debug -w iwd -w test -W meson

which explains why it only affects Fedora configurations.

It does not always fail, but the probability of failure is high.
The failure is:

  ...
  rm -f et.gmo && /usr/bin/msgmerge --for-msgfmt -o et.1po et.po NetworkManager.pot && /usr/bin/msgfmt -c --statistics --verbose -o et.gmo et.1po && rm -f et.1po
  libgomp: Thread creation failed: Resource temporarily unavailable
  make[3]: *** [Makefile:383: et.gmo] Error 1

Maybe some new resource restricting in gitlab. Let's add this workaround.
I don't really understand the cause, but this seems to avoid it, which is
good enough for me.
2023-01-19 19:31:28 +01:00
..
alpine-install.sh gitlab-ci: enable test build on alpine linux 2020-12-11 18:14:10 +01:00
ci.template gitlab-ci: add comment about how to regenerate ".gitlab-ci.yml" 2022-11-29 08:31:38 +01:00
config.yml gitlab-ci: bump ci-templates tag to generate new container images 2023-01-18 19:38:49 +01:00
debian-install.sh ci: drop Ubuntu 16.04 2022-06-27 13:40:09 +02:00
fedora-install.sh gitlab-ci: fix CentOS Linux 8 containers during ".gitlab-ci/fedora-install.sh" 2022-02-21 17:03:36 +01:00
run-test.sh gitlab-ci: set OMP_NUM_THREADS=1 to avoid libgomp crash for msgmerge 2023-01-19 19:31:28 +01:00