mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-28 13:20:08 +01:00
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.
This commit is contained in:
parent
f2db9be627
commit
01730f5943
1 changed files with 1 additions and 0 deletions
|
|
@ -3,6 +3,7 @@
|
|||
set -ex
|
||||
|
||||
export PAGER=cat
|
||||
export OMP_NUM_THREADS=1
|
||||
|
||||
IS_FEDORA=0
|
||||
IS_CENTOS=0
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue