From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
"Max Reitz" <mreitz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] travis: remove travis configuration and all references to Travis CI
Date: Tue, 9 Feb 2021 14:03:05 +0000 [thread overview]
Message-ID: <20210209140305.GK1166421@redhat.com> (raw)
In-Reply-To: <4e8492ab-9c10-d698-077a-9299b1a5b260@redhat.com>
On Tue, Feb 09, 2021 at 02:58:46PM +0100, Philippe Mathieu-Daudé wrote:
> On 2/9/21 2:50 PM, Daniel P. Berrangé wrote:
> > The Travis CI system QEMU has been using has removed the unlimited free
> > usage model, replacing it with a one-time only grant of CI minutes that
> > is not renewed. The QEMU CI jobs quickly exhaust maintainer's free CI
> > credits, leaving them unable to test with Travis. This is not a
> > sustainable situation, so we have no choice by to discontinue use of
> > Travis. GitLab CI is now the primary target, with Cirrus CI filling
> > in some platform gaps where needed.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > .travis.yml | 439 -----------------------------
> > MAINTAINERS | 3 -
> > configure | 1 -
> > contrib/gitdm/filetypes.txt | 2 +-
> > scripts/travis/coverage-summary.sh | 27 --
> > tests/docker/docker.py | 2 +-
> > tests/qemu-iotests/079 | 2 +-
> > tests/test-util-filemonitor.c | 11 -
> > 8 files changed, 3 insertions(+), 484 deletions(-)
> > delete mode 100644 .travis.yml
> > delete mode 100755 scripts/travis/coverage-summary.sh
> ...
>
> > diff --git a/configure b/configure
> > index 7c496d81fc..058a7c7967 100755
> > --- a/configure
> > +++ b/configure
> > @@ -4872,7 +4872,6 @@ fi
> > ########################################
> > # See if __attribute__((alias)) is supported.
> > # This false for Xcode 9, but has been remedied for Xcode 10.
>
> Not related to this patch, but I don't think Xcode 9 is supported
> anymore.
>
> > -# Unfortunately, travis uses Xcode 9 by default.
> >
> > attralias=no
> > cat > $TMPC << EOF
>
> > diff --git a/scripts/travis/coverage-summary.sh b/scripts/travis/coverage-summary.sh
> > deleted file mode 100755
> > index d7086cf9ca..0000000000
> > --- a/scripts/travis/coverage-summary.sh
> > +++ /dev/null
> > @@ -1,27 +0,0 @@
> > -#!/bin/sh
> > -#
> > -# Author: Alex Bennée <alex.bennee@linaro.org>
> > -#
> > -# Summerise the state of code coverage with gcovr and tweak the output
> > -# to be more sane on Travis hosts. As we expect to be executed on a
> > -# throw away CI instance we do spam temp files all over the shop. You
> > -# most likely don't want to execute this script but just call gcovr
> > -# directly. See also "make coverage-report"
> > -#
> > -# This code is licensed under the GPL version 2 or later. See
> > -# the COPYING file in the top-level directory.
> > -
> > -# first generate the coverage report
> > -gcovr -p -o raw-report.txt
> > -
> > -# strip the full-path and line markers
> > -sed s@$PWD\/@@ raw-report.txt | sed s/[0-9]\*[,-]//g > simplified.txt
> > -
> > -# reflow lines that got split
> > -awk '/.[ch]$/ { printf("%s", $0); next } 1' simplified.txt > rejoined.txt
> > -
> > -# columnify
> > -column -t rejoined.txt > final.txt
> > -
> > -# and dump, stripping out 0% coverage
> > -grep -v "0%" final.txt
>
> This script can be run on other CI.
>
> Keeping scripts/travis/coverage-summary.sh (moved to
> scripts/ci/coverage-summary.sh):
I notice that the "gcovr" program used here should be able to output
an XML document in a format that is supported by GitLab, which can
then pretty-display the results.
If we do that, perhaps we won't ned this coverage-summary script
for post-processing the text output format ?
I guess we need to make sure gcovr is actually installed in all
our dockerfiles used by gitlab.
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-02-09 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 13:50 [PATCH 0/2] travis: remove all use of Travis CI Daniel P. Berrangé
2021-02-09 13:50 ` [PATCH 1/2] tests/docker: remove travis container Daniel P. Berrangé
2021-02-11 12:20 ` Alex Bennée
2021-02-09 13:50 ` [PATCH 2/2] travis: remove travis configuration and all references to Travis CI Daniel P. Berrangé
2021-02-09 13:58 ` Philippe Mathieu-Daudé
2021-02-09 14:03 ` Daniel P. Berrangé [this message]
2021-02-09 14:15 ` Philippe Mathieu-Daudé
2021-02-09 14:32 ` Thomas Huth
2021-02-11 20:09 ` 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=20210209140305.GK1166421@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.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).