Skip to content
Snippets Groups Projects
Select Git revision
  • feature/libtcg-rebase default protected
1 result
Search by author
  • Any Author
  • Anton Anton anjo
1 author
  1. Jan 11, 2021
  3. Jan 02, 2021
  5. Dec 18, 2020
  7. Dec 09, 2020
  9. Nov 23, 2020
  11. Nov 10, 2020
  13. Nov 09, 2020
  15. Oct 27, 2020
  17. Oct 26, 2020
  19. Oct 17, 2020
  21. Oct 13, 2020
  23. Oct 12, 2020
    • Paolo Bonzini's avatar
      qemu-iotests, qtest: rewrite test 067 as a qtest · d8a18da5
      Paolo Bonzini authored 
      
Test 067 from qemu-iotests is executing QMP commands to hotplug
and hot-unplug disks, devices and blockdevs.  Because the power
of the text-based test harness is limited, it is actually limiting
the checks that it does, for example by skipping DEVICE_DELETED
events.

tests/qtest already has a similar test, drive_del-test.c.
We can merge them, and even reuse some of the existing code in
drive_del-test.c.  This will improve the quality of the test by
covering DEVICE_DELETED events and testing multiple architectures
(therefore covering multiple PCI hotplug mechanisms as well as s390x
virtio-ccw).

The only difference is that the new test will always use null-co:// for
the medium rather than qcow2 or raw, but this should be irrelevant for
what the test is covering.  For example there are no "qemu-img check"
runs in 067 that would check that the file is properly closed.

The new tests requires PCI hot-plug support, so drive_del-test
is moved from qemu-system-ppc to qemu-system-ppc64.

Reviewed-by: default avatarKevin Wolf <kwolf@redhat.com>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      d8a18da5
  25. Oct 02, 2020
  27. Sep 16, 2020
  29. Sep 07, 2020
    • Daniel P. Berrangé's avatar
      gitlab: expand test coverage for crypto builds · affcc09c
      Daniel P. Berrangé authored 
      
Most jobs test the latest nettle library. This adds explicit coverage
for latest gcrypt using Fedora, and old gcrypt and nettle using
CentOS-7. The latter does a minimal tools-only build, as we only need to
validate that the crypto code builds and unit tests pass. Finally a job
disabling both nettle and gcrypt is provided to validate that gnutls
still works.

Signed-off-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
Message-Id: <20200901133050.381844-3-berrange@redhat.com>
Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      affcc09c
    • Thomas Huth's avatar
      gitlab-ci: Add cross-compiling build tests · 6bcb5fc0
      Thomas Huth authored 
      
Now that we can use all our QEMU test containers in the gitlab-CI, we can
easily add some jobs that test cross-compilation for various architectures.
There is just only small ugliness: Since the shared runners on gitlab.com
are single-threaded, we have to split each compilation job into two parts
(--disable-user and --disable-system), and exclude some additional targets,
to avoid that the jobs are running too long and hitting the timeout of 1 h.

Message-Id: <20200823111757.72002-8-thuth@redhat.com>
Reviewed-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      6bcb5fc0
  31. Sep 03, 2020
  33. Aug 21, 2020
  35. Aug 05, 2020
    • Thomas Huth's avatar
      gitlab-ci: Fix Avocado cache usage · 5896c539
      Thomas Huth authored 
      
In commit 6957fd98 ("gitlab: add avocado asset caching") we
tried to save the Avocado cache (as in commit c1073e44 with
Travis-CI) however it doesn't work as expected. For some reason
Avocado uses /root/avocado_cache/ which we can not select later.

Manually generate a Avocado config to force the use of the
current job's directory.

This patch is based on an earlier version from Philippe Mathieu-Daudé.

Message-Id: <20200730141326.8260-5-thuth@redhat.com>
Reviewed-by: default avatarAlex Bennée <alex.bennee@linaro.org>
Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      5896c539
    • Thomas Huth's avatar
      gitlab-ci.yml: Add build-system-debian and build-system-centos jobs · 699616db
      Thomas Huth authored 
      
We were missing the two new targets avr-softmmu and rx-softmmu in the
gitlab-CI so far, and did not add some of the "other endianess" targets
like sh4eb-softmmu yet.
Since the current build-system-* jobs run already for a very long time,
let's do not add these missing targets there, but introduce two new
additional build jobs, one running with Debian and one running with
CentOS, and add the new targets there. Also move some targets from
the old build-system-* jobs to these new targets, to distribute the
load and reduce the runtime of the CI.

Message-Id: <20200730141326.8260-4-thuth@redhat.com>
Reviewed-by: default avatarAlex Bennée <alex.bennee@linaro.org>
Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      699616db
  37. Jul 21, 2020
  39. Jul 17, 2020
    • Thomas Huth's avatar
      gitlab-ci.yml: Add fuzzer tests · b610eba3
      Thomas Huth authored 
      
So far we neither compile-tested nor run any of the new fuzzers in our CI,
which led to some build failures of the fuzzer code in the past weeks.
To avoid this problem, add a job to compile the fuzzer code and run some
loops (which likely don't find any new bugs via fuzzing, but at least we
know that the code can still be run).

A nice side-effect of this test is that the leak tests are enabled here,
so we should now notice some of the memory leaks in our code base earlier.

Message-Id: <20200716100950.27396-1-thuth@redhat.com>
Reviewed-by: default avatarAlexander Bulekov <alxndr@bu.edu>
Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      b610eba3