kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, drjones@redhat.com
Subject: Re: [kvm-unit-tests PATCH] gitlab-ci.yml: Test build on CentOS 7
Date: Fri, 4 Sep 2020 16:00:25 +0200	[thread overview]
Message-ID: <5ed391a5-ad9f-c143-8286-71ec22497a83@redhat.com> (raw)
In-Reply-To: <20200731091548.8302-1-thuth@redhat.com>

On 31/07/2020 11.15, Thomas Huth wrote:
> We should also test our build with older versions of Bash and Gcc (at
> least the versions which we still want to support). CentOS 7 should be
> a reasonable base for such tests.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  .gitlab-ci.yml | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index d042cde..1ec9797 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -99,3 +99,20 @@ build-clang:
>       eventinj msr port80 setjmp syscall tsc rmap_chain umip intel_iommu
>       | tee results.txt
>   - grep -q PASS results.txt && ! grep -q FAIL results.txt
> +
> +build-centos7:
> + image: centos:7
> + before_script:
> + - yum update -y
> + - yum install -y make python qemu-kvm gcc
> + script:
> + - mkdir build
> + - cd build
> + - ../configure --arch=x86_64 --disable-pretty-print-stacks
> + - make -j2
> + - ACCEL=tcg ./run_tests.sh
> +     msr vmexit_cpuid vmexit_mov_from_cr8 vmexit_mov_to_cr8 vmexit_inl_pmtimer
> +     vmexit_ple_round_robin vmexit_tscdeadline vmexit_tscdeadline_immed port80
> +     setjmp sieve tsc rmap_chain umip
> +     | tee results.txt
> + - grep -q PASS results.txt && ! grep -q FAIL results.txt
> 

Ping!

Paolo, Drew, any comments on this one?

 Thomas


  reply	other threads:[~2020-09-04 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31  9:15 [kvm-unit-tests PATCH] gitlab-ci.yml: Test build on CentOS 7 Thomas Huth
2020-09-04 14:00 ` Thomas Huth [this message]
2020-09-04 14:21   ` Paolo Bonzini

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=5ed391a5-ad9f-c143-8286-71ec22497a83@redhat.com \
    --to=thuth@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@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).