Thomas Huth <[email protected]> writes:
> On 09/10/2019 21.06, Philippe Mathieu-Daudé wrote: >> On 10/9/19 7:07 PM, Thomas Huth wrote: >>> Travis now features an arm64 build host, so let's check compilation >>> there, too. >>> >>> Unfortunately, there are some quirks: >>> - block/ssh.c does not compile properly in this environment, so we have >>> to use --disable-libssh until that problem is fixed. >>> - test-util-filemonitor fails, so we can not run the unit tests there >>> - The file system size seems to be very limited, so the iotest tests >>> can't be used and the hd-geo-test fails (thus we can't compile >>> x86_64-softmmu here and run "check-qtest" afterwards) >>> - Compiling seems to be quite a bit slower than on the x86 builders, >>> so we better limit the target list to some few architectures. >>> >>> Signed-off-by: Thomas Huth <[email protected]> >>> --- >>> .travis.yml | 6 ++++++ >>> 1 file changed, 6 insertions(+) >>> >>> diff --git a/.travis.yml b/.travis.yml >>> index 0c88e8757b..357ca02890 100644 >>> --- a/.travis.yml >>> +++ b/.travis.yml >>> @@ -342,3 +342,9 @@ matrix: >>> - >>> CONFIG="--target-list=xtensa-softmmu,arm-softmmu,aarch64-softmmu,alpha-softmmu" >>> >>> - TEST_CMD="make -j3 check-tcg V=1" >>> - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default" >>> + >>> + # Non-x86 builds: >>> + - env: >>> + - CONFIG="--disable-libssh >>> --target-list=aarch64-softmmu,ppc64-softmmu,s390x-softmmu,x86_64-linux-user" >>> >> >> Is aarch64 on aarch64 interesting? >> >> Do you know if we can use KVM there? > > I don't think that KVM is usable there, but at least this should give us > some compile coverage for target/arm/kvm.c which we don't get > otherwise. We get compile coverage for !x86 kvm from the cross compilers on shippable. I'm more interested in running tests on !x86. > > Thomas -- Alex Bennée
