public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/python3.13] epel9: CI: Run the full test suites near the end
Date: Thu, 19 Nov 2026 11:12:18 GMT	[thread overview]
Message-ID: <179508673813.1.18365992564820218553.rpms-python3.13-0386ab0d361d@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python3.13
            Branch : epel9
            Commit : 0386ab0d361d4cd9a4d9ae2798374a21e4babc0d
            Author : Miro Hrončok <miro@hroncok.cz>
            Date   : 2026-10-30T14:50:18+01:00
            Stats  : +6/-6 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python3.13/c/0386ab0d361d4cd9a4d9ae2798374a21e4babc0d?branch=epel9

            Log:
            CI: Run the full test suites near the end

Now when the CI is running, we can see already completed tests.
This moves the most time expensive tests at the end,
so we can get a faster feedback loop if something other breaks.

Keeps required_symbols at the end, as it reinstalls Python and that can fail.

[skip changelog]

(cherry picked from python3.16 commit 6526b782b460346ed4b19c11bafec14bbc6499d4)

---
diff --git a/plan.fmf b/plan.fmf
index 41105ea..356e547 100644
--- a/plan.fmf
+++ b/plan.fmf
@@ -22,12 +22,6 @@ discover:
     - name: debugsmoke
       path: /smoke
       test: "PYTHON=python${pybasever}d TOX=false VERSION=${pybasever} CYTHON=false ./venv.sh"
-    - name: selftest
-      path: /selftest
-      test: "VERSION=${pybasever} X='-i test_check_probes' ./parallel.sh"
-    - name: debugtest
-      path: /selftest
-      test: "VERSION=${pybasever} PYTHON=python${pybasever}d X='-i test_check_probes' ./parallel.sh"
     - name: optimizedflags
       path: /flags
       test: "python${pybasever} ./assertflags.py -O3 CFLAGS PY_BUILTIN_MODULE_CFLAGS PY_CFLAGS PY_CORE_CFLAGS PY_CFLAGS_NODIST PY_STDMODULE_CFLAGS"
@@ -46,6 +40,12 @@ discover:
     - name: certifi
       path: /certifi
       test: "VERSION=${pybasever} ./certifi.sh"
+    - name: selftest
+      path: /selftest
+      test: "VERSION=${pybasever} X='-i test_check_probes' ./parallel.sh"
+    - name: debugtest
+      path: /selftest
+      test: "VERSION=${pybasever} PYTHON=python${pybasever}d X='-i test_check_probes' ./parallel.sh"
     - name: required_symbols
       path: /required-symbols
       test: "VERSION=${pybasever} ./check.sh"

                 reply	other threads:[~2026-11-19 11:12 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=179508673813.1.18365992564820218553.rpms-python3.13-0386ab0d361d@fedoraproject.org \
    --to=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