Skip to content
Snippets Groups Projects
  1. Jan 02, 2021
  2. Dec 09, 2020
  3. Nov 23, 2020
  4. Oct 17, 2020
  5. Oct 03, 2020
  6. Oct 02, 2020
  7. Sep 29, 2020
  8. Sep 16, 2020
  9. Sep 10, 2020
  10. Sep 03, 2020
    • Thomas Huth's avatar
      gitlab/travis: Rework the disabled features tests · a7524adb
      Thomas Huth authored
      
      Let's focus on the gitlab-ci when testing the compilation with disabled
      features, thus add more switches there (and while we're at it, sort them
      also alphabetically). This should cover the test from the Travis CI now,
      too, so that we can remove the now-redundant job from the Travis CI.
      
      Message-Id: <20200806155306.13717-1-thuth@redhat.com>
      Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      a7524adb
  11. Jul 15, 2020
    • Alex Bennée's avatar
      .travis.yml: skip ppc64abi32-linux-user with plugins · 0571d280
      Alex Bennée authored
      
      We actually see failures on threadcount running without plugins:
      
        retry.py -n 1000 -c -- \
          ./ppc64abi32-linux-user/qemu-ppc64abi32 \
          ./tests/tcg/ppc64abi32-linux-user/threadcount
      
      which reports:
      
        0: 978 times (97.80%), avg time 0.270 (0.01 varience/0.08 deviation)
        -6: 21 times (2.10%), avg time 0.336 (0.01 varience/0.12 deviation)
        -11: 1 times (0.10%), avg time 0.502 (0.00 varience/0.00 deviation)
        Ran command 1000 times, 978 passes
      
      But when running with plugins we hit the failure a lot more often:
      
        0: 91 times (91.00%), avg time 0.302 (0.04 varience/0.19 deviation)
        -11: 9 times (9.00%), avg time 0.558 (0.01 varience/0.11 deviation)
        Ran command 100 times, 91 passes
      
      The crash occurs in guest code which is the same in both pass and fail
      cases. However we see various messages reported on the console about
      corrupted memory lists which seems to imply the guest memory allocation
      is corrupted. This lines up with the seg fault being in the guest
      __libc_free function. So we think this is a guest bug which is
      exacerbated by various modes of translation. If anyone has access to
      real hardware to soak test the test case we could prove this properly.
      
      Signed-off-by: default avatarAlex Bennée <alex.bennee@linaro.org>
      Acked-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
      Reviewed-by: default avatarPhilippe Mathieu-Daudé <f4bug@amsat.org>
      Tested-by: default avatarPhilippe Mathieu-Daudé <f4bug@amsat.org>
      Message-Id: <20200714175516.5475-1-alex.bennee@linaro.org>
      0571d280
  12. Jul 11, 2020
  13. Jun 15, 2020
  14. Jun 08, 2020
  15. May 27, 2020
  16. May 15, 2020
  17. May 06, 2020
  18. Apr 06, 2020
  19. Mar 27, 2020
  20. Mar 17, 2020
    • Cleber Rosa's avatar
      Acceptance test: add "boot_linux" tests · 6fd52d67
      Cleber Rosa authored
      
      This acceptance test, validates that a full blown Linux guest can
      successfully boot in QEMU.  In this specific case, the guest chosen is
      Fedora version 31.
      
       * x86_64, pc-i440fx and pc-q35 machine types, with TCG and KVM as
         accelerators
      
       * aarch64 and virt machine type, with TCG and KVM as accelerators
      
       * ppc64 and pseries machine type with TCG as accelerator
      
       * s390x and s390-ccw-virtio machine type with TCG as accelerator
      
      The Avocado vmimage utils library is used to download and cache the
      Linux guest images, and from those images a snapshot image is created
      and given to QEMU.  If a qemu-img binary is available in the build
      directory, it's used to create the snapshot image, so that matching
      qemu-system-* and qemu-img are used in the same test run.  If qemu-img
      is not available in the build tree, one is attempted to be found
      installed system-wide (in the $PATH).  If qemu-img is not found in the
      build dir or in the $PATH, the test is canceled.
      
      The method for checking the successful boot is based on "cloudinit"
      and its "phone home" feature.  The guest is given an ISO image with
      the location of the phone home server, and the information to post
      (the instance ID).  Upon receiving the correct information, from the
      guest, the test is considered to have PASSed.
      
      This test is currently limited to user mode networking only, and
      instructs the guest to connect to the "router" address that is hard
      coded in QEMU.
      
      To create the cloudinit ISO image that will be used to configure the
      guest, the pycdlib library is also required and has been added as
      requirement to the virtual environment created by "check-venv".
      
      The console output is read by a separate thread, by means of the
      Avocado datadrainer utility module.
      
      Signed-off-by: default avatarCleber Rosa <crosa@redhat.com>
      Reviewed-by: default avatarWainer dos Santos Moschetta <wainersm@redhat.com>
      Reviewed-by: default avatarWillian Rampazzo <willianr@redhat.com>
      Tested-by: default avatarWillian Rampazzo <willianr@redhat.com>
      Message-Id: <20200317141654.29355-3-crosa@redhat.com>
      Signed-off-by: default avatarCleber Rosa <crosa@redhat.com>
      6fd52d67
    • Philippe Mathieu-Daudé's avatar
      travis.yml: Set G_MESSAGES_DEBUG do report GLib errors · 2dbd39c2
      Philippe Mathieu-Daudé authored
      
      Since commit f5852efa we can display GLib errors with the QEMU
      error reporting API. Set it to the 'error' level, as this helps
      understanding failures from QEMU calls to GLib on Travis-CI.
      
      Signed-off-by: default avatarPhilippe Mathieu-Daudé <philmd@redhat.com>
      Signed-off-by: default avatarAlex Bennée <alex.bennee@linaro.org>
      Message-Id: <20200316101544.22361-1-philmd@redhat.com>
      Message-Id: <20200316172155.971-6-alex.bennee@linaro.org>
      2dbd39c2
  21. Mar 04, 2020
  22. Feb 28, 2020
  23. Feb 25, 2020
  24. Feb 07, 2020
Loading