diff options
author | Thomas Haller <thaller@redhat.com> | 2023-01-19 18:42:43 +0100 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2023-01-19 19:31:28 +0100 |
commit | 01730f5943019c3fed2eeaa19cebca47c6a9ef4a (patch) | |
tree | 008cb591fff0efeafe4a3848231a2c47db5d6ed7 /meson.build | |
parent | f2db9be627fe12d22e6d04c8a211e5a9a0abc25c (diff) | |
download | NetworkManager-01730f5943019c3fed2eeaa19cebca47c6a9ef4a.tar.gz |
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.
Diffstat (limited to 'meson.build')
0 files changed, 0 insertions, 0 deletions