From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P . Berrange" <berrange@redhat.com>
Subject: [PATCH v2 14/15] gitlab-ci: Update QEMU_JOB_AVOCADO and QEMU_CI_AVOCADO_TESTING
Date: Mon, 14 Apr 2025 13:30:28 +0200 [thread overview]
Message-ID: <20250414113031.151105-15-thuth@redhat.com> (raw)
In-Reply-To: <20250414113031.151105-1-thuth@redhat.com>
From: Thomas Huth <thuth@redhat.com>
Since we don't run the Avocado jobs in the CI anymore, rename
these variables to QEMU_JOB_FUNCTIONAL and QEMU_CI_FUNCTIONAL.
Also, there was a mismatch between the documentation and the
implementation of QEMU_CI_AVOCADO_TESTING: While the documentation
said that you had to "Set this variable to have the tests using the
Avocado framework run automatically", you indeed needed to set it
to make the pipelines appear in your dashboard - but they were never
run automatically in forks and had to be triggered manually. Let's
improve this now: No need to hide these pipelines from the users
by default anymore (the functional tests should be stable enough
nowadays), and rather allow the users to run the pipelines auto-
matically with this switch now instead, as was documented.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
docs/devel/testing/ci-jobs.rst.inc | 19 +++++++++----------
.gitlab-ci.d/base.yml | 8 ++------
.gitlab-ci.d/buildtest-template.yml | 2 +-
3 files changed, 12 insertions(+), 17 deletions(-)
diff --git a/docs/devel/testing/ci-jobs.rst.inc b/docs/devel/testing/ci-jobs.rst.inc
index 3756bbe3554..f1c541cc25b 100644
--- a/docs/devel/testing/ci-jobs.rst.inc
+++ b/docs/devel/testing/ci-jobs.rst.inc
@@ -126,10 +126,10 @@ QEMU_JOB_PUBLISH
The job is for publishing content after a branch has been
merged into the upstream default branch.
-QEMU_JOB_AVOCADO
-~~~~~~~~~~~~~~~~
+QEMU_JOB_FUNCTIONAL
+~~~~~~~~~~~~~~~~~~~
-The job runs the Avocado integration test suite
+The job runs the functional test suite
Contributor controlled runtime variables
----------------------------------------
@@ -149,13 +149,12 @@ the jobs to be manually started from the UI
Set this variable to 2 to create the pipelines and run all
the jobs immediately, as was the historical behaviour
-QEMU_CI_AVOCADO_TESTING
-~~~~~~~~~~~~~~~~~~~~~~~
-By default, tests using the Avocado framework are not run automatically in
-the pipelines (because multiple artifacts have to be downloaded, and if
-these artifacts are not already cached, downloading them make the jobs
-reach the timeout limit). Set this variable to have the tests using the
-Avocado framework run automatically.
+QEMU_CI_FUNCTIONAL
+~~~~~~~~~~~~~~~~~~
+By default, tests using the functional framework are not run automatically
+in the pipelines (because multiple artifacts have to be downloaded, which
+might cause a lot of network traffic). Set this variable to have the tests
+using the functional framework run automatically.
Other misc variables
--------------------
diff --git a/.gitlab-ci.d/base.yml b/.gitlab-ci.d/base.yml
index 25b88aaa06a..60a24a9d14d 100644
--- a/.gitlab-ci.d/base.yml
+++ b/.gitlab-ci.d/base.yml
@@ -69,10 +69,6 @@ variables:
- if: '$QEMU_CI != "1" && $QEMU_CI != "2" && $CI_PROJECT_NAMESPACE != $QEMU_CI_UPSTREAM'
when: never
- # Avocado jobs don't run in forks unless $QEMU_CI_AVOCADO_TESTING is set
- - if: '$QEMU_JOB_AVOCADO && $QEMU_CI_AVOCADO_TESTING != "1" && $CI_PROJECT_NAMESPACE != $QEMU_CI_UPSTREAM'
- when: never
-
#############################################################
# Stage 2: fine tune execution of jobs in specific scenarios
@@ -101,8 +97,8 @@ variables:
when: manual
allow_failure: true
- # Avocado jobs can be manually start in forks if $QEMU_CI_AVOCADO_TESTING is unset
- - if: '$QEMU_JOB_AVOCADO && $CI_PROJECT_NAMESPACE != $QEMU_CI_UPSTREAM'
+ # Functional jobs can be manually started in forks
+ - if: '$QEMU_JOB_FUNCTIONAL && $QEMU_CI_FUNCTIONAL != "1" && $CI_PROJECT_NAMESPACE != $QEMU_CI_UPSTREAM'
when: manual
allow_failure: true
diff --git a/.gitlab-ci.d/buildtest-template.yml b/.gitlab-ci.d/buildtest-template.yml
index 13fa4f4a4fc..d4f145fdb58 100644
--- a/.gitlab-ci.d/buildtest-template.yml
+++ b/.gitlab-ci.d/buildtest-template.yml
@@ -114,4 +114,4 @@
- cd build
- du -chs ${CI_PROJECT_DIR}/*-cache
variables:
- QEMU_JOB_AVOCADO: 1
+ QEMU_JOB_FUNCTIONAL: 1
--
2.49.0
next prev parent reply other threads:[~2025-04-14 11:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 11:30 [PATCH v2 00/15] Convert remaining Avocado tests to functional Thomas Huth
2025-04-14 11:30 ` [PATCH v2 01/15] gitlab-ci: Remove the avocado tests from the CI pipelines Thomas Huth
2025-04-14 11:30 ` [PATCH v2 02/15] tests/functional: Move the check for the parameters from avocado to functional Thomas Huth
2025-04-14 11:30 ` [PATCH v2 03/15] tests/functional: Convert reverse_debugging tests to the functional framework Thomas Huth
2025-04-14 11:51 ` Daniel P. Berrangé
2025-04-14 11:30 ` [PATCH v2 04/15] tests/functional: Convert the i386 replay avocado test Thomas Huth
2025-04-14 11:30 ` [PATCH v2 05/15] tests/avocado: Remove the LinuxKernelTest class Thomas Huth
2025-04-14 11:30 ` [PATCH v2 06/15] tests/functional: Convert the 32-bit big endian Wheezy mips test Thomas Huth
2025-04-14 11:30 ` [PATCH v2 07/15] tests/functional: Convert the 32-bit little " Thomas Huth
2025-04-14 11:30 ` [PATCH v2 08/15] tests/functional: Convert the 64-bit " Thomas Huth
2025-04-14 11:30 ` [PATCH v2 09/15] tests/functional: Convert the 64-bit big " Thomas Huth
2025-04-14 11:30 ` [PATCH v2 10/15] tests/avocado: Remove the boot_linux.py tests Thomas Huth
2025-04-14 11:30 ` [PATCH v2 11/15] tests/functional: Use the tuxrun kernel for the x86 replay test Thomas Huth
2025-04-14 11:30 ` [PATCH v2 12/15] tests/functional: Use the tuxrun kernel for the aarch64 " Thomas Huth
2025-04-14 11:30 ` [PATCH v2 13/15] tests/functional: Convert the SMMU test to the functional framework Thomas Huth
2025-04-14 11:30 ` Thomas Huth [this message]
2025-04-14 11:30 ` [PATCH v2 15/15] Remove the remainders of the Avocado tests Thomas Huth
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=20250414113031.151105-15-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).