Re: [kvm-unit-tests PATCH v2 10/10] travis.yml: Add x86 build with clang 10

[Thomas Huth <thuth@redhat.com>]

On 01/09/2020 10.50, Roman Bolshakov wrote:
> .gitlab-ci.yml already has a job to build the tests with clang but it's
> not clear how to set it up on a personal github repo.

You can't use gitlab-ci from a github repo, it's a separate git forge
system.

> NB, realmode test is disabled because it fails immediately after start
> if compiled with clang-10.
> 
> Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com>
> ---
>  .travis.yml | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index f3a8899..ae4ed08 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -17,6 +17,16 @@ jobs:
>                 kvmclock_test msr pcid rdpru realmode rmap_chain s3 setjmp umip"
>        - ACCEL="kvm"
>  
> +    - addons:
> +        apt_packages: clang-10 qemu-system-x86
> +      env:
> +      - CONFIG="--cc=clang-10"
> +      - BUILD_DIR="."
> +      - TESTS="access asyncpf debug emulator ept hypercall hyperv_stimer
> +               hyperv_synic idt_test intel_iommu ioapic ioapic-split
> +               kvmclock_test msr pcid rdpru rmap_chain s3 setjmp umip"
> +      - ACCEL="kvm"

We already have two jobs for compiling on x86, one for testing in-tree
builds and one for testing out-of-tree builds ... I wonder whether we
should simply switch one of those two jobs to use clang-10 instead of
gcc (since the in/out-of-tree stuff should be hopefully independent of
the compiler type)? Since Travis limits the amount of jobs that run at
the same time, that would not increase the total testing time, I think.

 Thomas


PS: Maybe we could update from bionic to focal now, too, and see whether
some more tests are working with the newer version of QEMU there...