Skip to content
Snippets Groups Projects
  1. Oct 12, 2021
  2. Jul 14, 2021
  3. Feb 19, 2021
  4. Feb 15, 2021
  5. Jan 18, 2021
  6. Jan 02, 2021
  7. Dec 09, 2020
  8. Nov 23, 2020
  9. Oct 17, 2020
  10. Oct 03, 2020
  11. Oct 02, 2020
  12. Sep 29, 2020
  13. Sep 16, 2020
  14. Sep 10, 2020
  15. 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
  16. 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
  17. Jul 11, 2020
  18. Jun 15, 2020
  19. Jun 08, 2020
  20. May 27, 2020
  21. May 15, 2020
  22. May 06, 2020
  23. Apr 06, 2020
Loading