public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Frantisek Sumsal <frantisek@sumsal.cz>
To: git-commits@fedoraproject.org
Subject: [rpms/systemd] rawhide: test: cap the number of parallel tests
Date: Mon, 06 Jul 2026 18:55:25 GMT	[thread overview]
Message-ID: <178336412555.1.16259313112895401824.rpms-systemd-c53b2fb30757@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/systemd
            Branch : rawhide
            Commit : c53b2fb30757ef43cd4c7288fb014ebc0785fa3b
            Author : Frantisek Sumsal <frantisek@sumsal.cz>
            Date   : 2026-07-06T17:26:40+00:00
            Stats  : +4/-5 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/systemd/c/c53b2fb30757ef43cd4c7288fb014ebc0785fa3b?branch=rawhide

            Log:
            test: cap the number of parallel tests

Cap the number of parallel tests to 4 to not overwhelm beefier hosts.

I tried this with 8 jobs, but it often caused annoying timeouts in
nspawn-based tests; maybe this could be investigated and potentially
addressed in the future.

[skip changelog]

---
diff --git a/plans/run-integration-tests.sh b/plans/run-integration-tests.sh
index 6d2ee37..d9edd5d 100755
--- a/plans/run-integration-tests.sh
+++ b/plans/run-integration-tests.sh
@@ -89,16 +89,15 @@ if [[ ! -e /dev/kvm ]]; then
 fi
 
 NPROC="$(nproc)"
-if [[ "$NPROC" -ge 10 ]]; then
-    export TEST_JOURNAL_USE_TMP=1
-    NPROC="$((NPROC / 3))"
-else
-    NPROC="$((NPROC - 1))"
+if [[ "$NPROC" -gt 4 ]]; then
+    # Cap the number of parallel tests to 4 to not overwhelm larger hosts
+    NPROC=4
 fi
 
 # This test is only really useful if we're building with sanitizers and takes a long time, so let's skip it
 # for now.
 export TEST_SKIP="TEST-21-DFUZZER ${TEST_SKIP:-}"
+export TEST_JOURNAL_USE_TMP=1
 
 mkosi genkey
 mkosi summary

                 reply	other threads:[~2026-07-06 18:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178336412555.1.16259313112895401824.rpms-systemd-c53b2fb30757@fedoraproject.org \
    --to=frantisek@sumsal.cz \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox