From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Roger Pau Monne <roger.pau@citrix.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [PATCH 2/2] automation: introduce non debug clang based tests
Date: Thu, 29 Feb 2024 10:55:29 +0100 [thread overview]
Message-ID: <20240229095529.17723-3-roger.pau@citrix.com> (raw)
In-Reply-To: <20240229095529.17723-1-roger.pau@citrix.com>
The generated code between the debug and release builds can be quite
different, as a note 2ce562b2a413 only manifested in non-debug builds due to
the usage of -O2.
Duplicate the clang based test in order to test with both debug and non-debug
Xen builds.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
automation/gitlab-ci/test.yaml | 18 ++++++++++++++++--
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
index 8b7b2e4da92d..dedca794b257 100644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -422,13 +422,20 @@ qemu-smoke-x86-64-gcc:
needs:
- debian-stretch-gcc-debug
-qemu-smoke-x86-64-clang:
+qemu-smoke-x86-64-clang-debug:
extends: .qemu-x86-64
script:
- ./automation/scripts/qemu-smoke-x86-64.sh pv 2>&1 | tee ${LOGFILE}
needs:
- debian-bookworm-clang-debug
+qemu-smoke-x86-64-clang:
+ extends: .qemu-x86-64
+ script:
+ - ./automation/scripts/qemu-smoke-x86-64.sh pv 2>&1 | tee ${LOGFILE}
+ needs:
+ - debian-bookworm-clang
+
qemu-smoke-x86-64-gcc-pvh:
extends: .qemu-x86-64
script:
@@ -436,13 +443,20 @@ qemu-smoke-x86-64-gcc-pvh:
needs:
- debian-stretch-gcc-debug
-qemu-smoke-x86-64-clang-pvh:
+qemu-smoke-x86-64-clang-debug-pvh:
extends: .qemu-x86-64
script:
- ./automation/scripts/qemu-smoke-x86-64.sh pvh 2>&1 | tee ${LOGFILE}
needs:
- debian-bookworm-clang-debug
+qemu-smoke-x86-64-clang-pvh:
+ extends: .qemu-x86-64
+ script:
+ - ./automation/scripts/qemu-smoke-x86-64.sh pvh 2>&1 | tee ${LOGFILE}
+ needs:
+ - debian-bookworm-clang
+
qemu-smoke-riscv64-gcc:
extends: .qemu-riscv64
script:
--
2.44.0
next prev parent reply other threads:[~2024-02-29 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 9:55 [PATCH 0/2] Restrict Clang/LLVM supported versions Roger Pau Monne
2024-02-29 9:55 ` [PATCH 1/2] README: bump minimum required clang/llvm version Roger Pau Monne
2024-02-29 12:11 ` Jan Beulich
2024-02-29 12:40 ` Roger Pau Monné
2024-02-29 13:01 ` Jan Beulich
2024-02-29 13:12 ` Jan Beulich
2024-02-29 14:21 ` Roger Pau Monné
2024-02-29 14:28 ` Jan Beulich
2024-03-12 22:45 ` Julien Grall
2024-02-29 9:55 ` Roger Pau Monne [this message]
2024-03-05 17:29 ` [PATCH 2/2] automation: introduce non debug clang based tests Roger Pau Monné
2024-03-07 22:15 ` Stefano Stabellini
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=20240229095529.17723-3-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=cardoe@cardoe.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.