1. 08 Feb, 2021 2 commits
  2. 26 Oct, 2020 2 commits
  3. 20 Jul, 2020 2 commits
  4. 01 May, 2020 1 commit
  5. 19 Mar, 2020 4 commits
  6. 17 Mar, 2020 2 commits
  7. 16 Dec, 2019 1 commit
  8. 27 Nov, 2019 1 commit
  9. 04 Oct, 2019 1 commit
  10. 22 Jul, 2019 1 commit
  11. 18 Jul, 2019 1 commit
    • Frediano Ziglio's avatar
      ci: Workaround an issue with GLib on Fedora 30 · 89edf808
      Frediano Ziglio authored
      This remove this error running test-listen test on a Fedora 30 docker
      image:
      
      (/builds/spice/spice/build/server/tests/test-listen:2233): GLib-GIO-CRITICAL **: 15:29:03.123: g_file_new_for_path: assertion 'path != NULL' failed
      
      This error is due to some missing configuration on the image.
      On a fully installed Desktop/Server machine these configuration
      are usually in place so you won't note the issue but on recent
      docker images these configuration are missing.
      
      Running the dconf command add required configuration.
      Signed-off-by: Frediano Ziglio's avatarFrediano Ziglio <fziglio@redhat.com>
      Acked-by: Uri Lublin's avatarUri Lublin <uril@redhat.com>
      89edf808
  12. 26 Jun, 2019 1 commit
  13. 13 Jun, 2019 2 commits
  14. 07 May, 2019 1 commit
  15. 01 May, 2019 1 commit
  16. 23 Jan, 2019 1 commit
  17. 08 Nov, 2018 1 commit
  18. 28 Sep, 2018 1 commit
  19. 31 Aug, 2018 1 commit
  20. 30 Aug, 2018 1 commit
  21. 11 Jul, 2018 1 commit
  22. 19 Jun, 2018 1 commit
  23. 14 Jun, 2018 1 commit
  24. 17 Apr, 2018 1 commit
    • Frediano Ziglio's avatar
      ci: Workaround bug in Valgrind detecting memcpy instead of memmove · ac05eee0
      Frediano Ziglio authored
      Due to a bug in current packaged Valgrind in the CI (1:3.13.0-13.fc27)
      check-valgrind is failing with:
      
      ==17986== Source and destination overlap in memcpy_chk(0x72c060, 0x72c068, 33)
      ==17986==    at 0x4C344F0: __memcpy_chk (vg_replace_strmem.c:1581)
      ==17986==    by 0x40E7E9: check_vmc_error_message (test-stream-device.c:166)
      ==17986==    by 0x40EFD4: test_stream_device_format_after_data (test-stream-device.c:349)
      ==17986==    by 0x7A012E9: test_case_run (gtestutils.c:2157)
      ==17986==    by 0x7A012E9: g_test_run_suite_internal (gtestutils.c:2241)
      ==17986==    by 0x7A0121A: g_test_run_suite_internal (gtestutils.c:2253)
      ==17986==    by 0x7A014C1: g_test_run_suite (gtestutils.c:2329)
      ==17986==    by 0x7A014E0: g_test_run (gtestutils.c:1594)
      ==17986==    by 0x40951A: main (test-stream-device.c:410)
      ==17986==
      
      By default during CI build _FORTIFY_SOURCE is enabled, which turns memmove
      into __memmove_chk, which is wrongly turned into __memcpy_chk when running
      under Valgrind.
      Setting _FORTIFY_SOURCE to 0 prevents the use of __memmove_chk, and avoids
      triggering the Valgrind bug.
      Signed-off-by: Frediano Ziglio's avatarFrediano Ziglio <fziglio@redhat.com>
      Acked-by: Christophe Fergeau's avatarChristophe Fergeau <cfergeau@redhat.com>
      ac05eee0
  25. 14 Mar, 2018 1 commit
  26. 09 Mar, 2018 1 commit
  27. 28 Nov, 2017 1 commit
  28. 07 Nov, 2017 1 commit
  29. 01 Sep, 2017 1 commit
  30. 28 Jul, 2017 1 commit
  31. 23 Mar, 2017 1 commit
  32. 22 Mar, 2017 1 commit