From 01730f5943019c3fed2eeaa19cebca47c6a9ef4a Mon Sep 17 00:00:00 2001
From: Thomas Haller <thaller@redhat.com>
Date: Thu, 19 Jan 2023 18:42:43 +0100
Subject: [PATCH] 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.
---
 .gitlab-ci/run-test.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitlab-ci/run-test.sh b/.gitlab-ci/run-test.sh
index 853e5132c..c8fe8016f 100755
--- a/.gitlab-ci/run-test.sh
+++ b/.gitlab-ci/run-test.sh
@@ -3,6 +3,7 @@
 set -ex
 
 export PAGER=cat
+export OMP_NUM_THREADS=1
 
 IS_FEDORA=0
 IS_CENTOS=0