Thomas Haller 3bad3f8b24 gitlab-ci: fix randomizing tests in "nm-ci-run.sh" ... The code was just wrong. Usually in gitlab-ci, NMTST_SEED_RANDOM is unset, so the previous code would not have set it. Which means that our tests run with NMTST_SEED_RANDOM="0". Fuzzing (or randomizing tests) is very useful, we should do that for the unit tests that run in gitlab-ci. Fix this. But don't let the test choose a random number. Instead, let the calling script choose it. That is, because we might run the tests more than once (without debugging and no valgrind; in case of failure return with debugging; with valgrind). Those runs should use the same seed. This fixes commit 70487d9ff8 ('ci: randomize tests during our CI'), but as fixing randomization can break previously running tests, we may only want to backport this commit after careful evaluation.		2023-01-30 08:18:45 +01:00
..
alpine	contrib/packages: install pexpect	2022-06-30 10:20:44 +02:00
art/logo	artwork: introduce NetworkManager stickers	2019-09-30 17:36:59 +02:00
debian	gitlab-ci: ignore failure to install "python-setuptools" on debian	2022-11-29 19:54:19 +01:00
editors
fedora	contrib/rpm: fix condition in "NetworkManager.spec" (3)	2023-01-24 12:29:04 +01:00
scripts	gitlab-ci: fix randomizing tests in "nm-ci-run.sh"	2023-01-30 08:18:45 +01:00