From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Willian Rampazzo" <wrampazz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 1/6] travis.yml: Move gprof/gcov test across to gitlab
Date: Thu, 04 Feb 2021 10:12:20 +0000 [thread overview]
Message-ID: <87pn1gqgwo.fsf@linaro.org> (raw)
In-Reply-To: <94efc386-3c6c-81e3-46d9-650351f92248@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> On 03/02/2021 20.32, Wainer dos Santos Moschetta wrote:
>> Hi,
>>
>> On 2/3/21 8:32 AM, Thomas Huth wrote:
>>> From: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>
>>> Similarly to commit 8cdb2cef3f1, move the gprof/gcov test to GitLab.
>>>
>>> The coverage-summary.sh script is not Travis-CI specific, make it
>>> generic.
>>>
>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>> Message-Id: <20201108204535.2319870-10-philmd@redhat.com>
>>> [thuth: Add gcovr and bsdmainutils which are required for the
>>> overage-summary.sh script to the ubuntu docker file]
>> s/overage/coverage/
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>> .gitlab-ci.yml | 12 ++++++++++++
>>> .travis.yml | 14 --------------
>>> MAINTAINERS | 2 +-
>>> scripts/{travis => ci}/coverage-summary.sh | 2 +-
>>> tests/docker/dockerfiles/ubuntu2004.docker | 2 ++
>>> 5 files changed, 16 insertions(+), 16 deletions(-)
>>> rename scripts/{travis => ci}/coverage-summary.sh (92%)
>>>
>>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>> index 7c0db64710..8b97b512bb 100644
>>> --- a/.gitlab-ci.yml
>>> +++ b/.gitlab-ci.yml
>>> @@ -468,6 +468,18 @@ check-deprecated:
>>> MAKE_CHECK_ARGS: check-tcg
>>> allow_failure: true
>>> +# gprof/gcov are GCC features
>>> +build-gprof-gcov:
>>> + <<: *native_build_job_definition
>>> + variables:
>>> + IMAGE: ubuntu2004
>>> + CONFIGURE_ARGS: --enable-gprof --enable-gcov
>>> + MAKE_CHECK_ARGS: build-tcg
>>
>> With build-tcg it generates an empty report, e.g.,
>> https://gitlab.com/wainersm/qemu/-/jobs/1005923421
>>
>> Shouldn't it run `make check`?
>
> D'oh, you're right. I think we need to run at least a "make check-unit"
> here. I'll rework my patch accordingly...
>
> By the way, it's broken on Travis since a long time, e.g. with version 5.0
> there is already only a stack trace:
>
> https://travis-ci.org/github/qemu/qemu/jobs/680661167#L8411
>
> Seems like nobody noticed this for almost a year now...
doh - the check_coverage was an after_success step so never influenced
the result. It was only a band aid really though - it would be better if
we published the html coverage report on gitlab's pages (like we now do
for annotated gtags source: https://qemu-project.gitlab.io/qemu/src/
>
> Thomas
--
Alex Bennée
next prev parent reply other threads:[~2021-02-04 10:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 11:32 [PATCH 0/6] Move remaining x86 Travis jobs to the gitlab-CI Thomas Huth
2021-02-03 11:32 ` [PATCH 1/6] travis.yml: Move gprof/gcov test across to gitlab Thomas Huth
2021-02-03 19:32 ` Wainer dos Santos Moschetta
2021-02-04 6:58 ` Thomas Huth
2021-02-04 10:12 ` Alex Bennée [this message]
2021-02-03 11:32 ` [PATCH 2/6] travis.yml: Move the -fsanitize=undefined test to the gitlab-CI Thomas Huth
2021-02-03 11:32 ` [PATCH 3/6] travis.yml: Move the --enable-modules " Thomas Huth
2021-02-03 18:48 ` Wainer dos Santos Moschetta
2021-02-03 11:32 ` [PATCH 4/6] travis.yml: Remove the --enable-debug jobs Thomas Huth
2021-02-03 18:56 ` Wainer dos Santos Moschetta
2021-02-03 11:32 ` [PATCH 5/6] target/s390x/arch_dump: Fixes for the name field in the PT_NOTE section Thomas Huth
2021-02-03 11:32 ` [PATCH 6/6] travis.yml: Move the -fsanitize=thread compile-testing to the gitlab-CI Thomas Huth
2021-02-03 19:23 ` Wainer dos Santos Moschetta
2021-02-03 20:15 ` Wainer dos Santos Moschetta
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=87pn1gqgwo.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).