From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
peter.maydell@linaro.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH v1 6/6] gitlab-ci: Move trace backend tests across to gitlab
Date: Fri, 20 Nov 2020 15:35:03 +0100 [thread overview]
Message-ID: <c4c724ce-1e23-c4ae-f75f-dce0190504f7@redhat.com> (raw)
In-Reply-To: <7f383116-3974-bf41-66f1-23f884211257@redhat.com>
On 18/11/2020 10.54, Thomas Huth wrote:
> On 17/11/2020 18.36, Alex Bennée wrote:
>> From: Philippe Mathieu-Daudé <philmd@redhat.com>
>>
>> Similarly to commit 8cdb2cef3f1, move the trace backend
>> tests to GitLab.
>>
>> Note the User-Space Tracer backend is still tested on
>> Ubuntu by the s390x jobs on Travis-CI.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Message-Id: <20201111121234.3246812-3-philmd@redhat.com>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> .gitlab-ci.yml | 18 ++++++++++++++++++
>> .travis.yml | 19 -------------------
>> 2 files changed, 18 insertions(+), 19 deletions(-)
>>
>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> index b406027a55..d0173e82b1 100644
>> --- a/.gitlab-ci.yml
>> +++ b/.gitlab-ci.yml
>> @@ -415,6 +415,24 @@ check-crypto-only-gnutls:
>> IMAGE: centos7
>> MAKE_CHECK_ARGS: check
>>
>> +# We don't need to exercise every backend with every front-end
>> +build-trace-multi-user:
>> + <<: *native_build_job_definition
>> + variables:
>> + IMAGE: ubuntu2004
>> + CONFIGURE_ARGS: --enable-trace-backends=log,simple,syslog --disable-system
>> +
>> +build-trace-ftrace-system:
>> + <<: *native_build_job_definition
>> + variables:
>> + IMAGE: ubuntu2004
>> + CONFIGURE_ARGS: --enable-trace-backends=ftrace --target-list=x86_64-softmmu
>> +
>> +build-trace-ust-system:
>> + <<: *native_build_job_definition
>> + variables:
>> + IMAGE: ubuntu2004
>> + CONFIGURE_ARGS: --enable-trace-backends=ust --target-list=x86_64-softmmu
>
> Hmmm, do we really need separate build jobs for this, or could we maybe
> rather simply add the options to some existing jobs instead (to save some CI
> cycles)?
I guess we can still consolidate later ... but since Travis is now limiting
the CI minutes, we definitely have to move this over, so:
Acked-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-11-20 14:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 17:36 [PATCH for 5.3-rc3 v1 0/6] testing fixes (avocado, gitlab) Alex Bennée
2020-11-17 17:36 ` [PATCH v1 1/6] scripts/ci: clean up default args logic a little Alex Bennée
2020-11-20 20:42 ` Wainer dos Santos Moschetta
2020-11-17 17:36 ` [PATCH v1 2/6] tests: add prefixes to the bare mkdtemp calls Alex Bennée
2020-11-17 17:56 ` Philippe Mathieu-Daudé
2020-11-18 9:44 ` Thomas Huth
2020-11-20 18:55 ` Wainer dos Santos Moschetta
2020-11-17 17:36 ` [PATCH v1 3/6] tests/avocado: clean-up socket directory after run Alex Bennée
2020-11-20 18:59 ` Wainer dos Santos Moschetta
2020-11-23 9:23 ` Alex Bennée
2020-11-23 13:43 ` Wainer dos Santos Moschetta
2020-11-17 17:36 ` [PATCH v1 4/6] gitlab: move remaining x86 check-tcg targets to gitlab Alex Bennée
2020-11-18 9:51 ` Thomas Huth
2020-11-20 17:45 ` Wainer dos Santos Moschetta
2020-11-17 17:36 ` [PATCH v1 5/6] tests/docker: Install liblttng-ust-dev package in Ubuntu 20.04 image Alex Bennée
2020-11-17 17:36 ` [PATCH v1 6/6] gitlab-ci: Move trace backend tests across to gitlab Alex Bennée
2020-11-18 9:54 ` Thomas Huth
2020-11-20 14:35 ` Thomas Huth [this message]
2020-11-19 14:40 ` [PATCH for 5.2-rc3 v1 0/6] testing fixes (avocado, gitlab) Alex Bennée
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=c4c724ce-1e23-c4ae-f75f-dce0190504f7@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/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).