1. 03 Jun, 2019 1 commit
  2. 31 May, 2019 1 commit
    • Philip Withnall's avatar
      tests: Fix small race in GSubprocess tests · 7f256e63
      Philip Withnall authored
      This was introduced in commit 7846d615: g_subprocess_get_identifier()
      will return NULL after the subprocess has exited, and the subprocess in
      the `noop` test will exit as soon as it has started spawning. So if the
      scheduler scheduled the testprog subprocess quickly, descheduled the
      parent test process until the testprog exited, then the return value
      from g_subprocess_get_identifier() would be NULL.
      Move the g_subprocess_get_identifier() test to one which calls testprog
      in `sleep-forever` mode, since that is guaranteed not to exit until
      killed (which we do later in the test).
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
  3. 14 May, 2019 1 commit
  4. 10 May, 2019 1 commit
  5. 02 May, 2019 1 commit
  6. 27 Apr, 2019 1 commit
  7. 26 Apr, 2019 1 commit
  8. 25 Apr, 2019 1 commit
  9. 23 Apr, 2019 1 commit
  10. 22 Apr, 2019 1 commit
    • Emmanuele Bassi's avatar
      Remove monitor test · 5299e875
      Emmanuele Bassi authored
      The `monitor` test was originally written to test GFileMonitor with
      directories. Over time, `testfilemonitor` acquired units for testing
      directories as well, which made the `monitor` test reduntant.
  11. 12 Apr, 2019 4 commits
  12. 27 Mar, 2019 1 commit
    • LRN's avatar
      Check for RTLD_NEXT · a53ff746
      LRN authored
      Check for RTLD_NEXT being present, and disable the gsocketclient-slow
      test if it's absent, since the shlib dependency of that test requires
      RTLD_NEXT to function.
      This allows the testsuite to be built on Cygwin, which behaves
      exactly like UNIX, but doesn't have RTLD_NEXT.
  13. 15 Mar, 2019 9 commits
  14. 12 Mar, 2019 2 commits
    • Vasily Galkin's avatar
      gdbus, tests, win32: test session dbus autolaunch · b245344c
      Vasily Galkin authored
      The test performs implicit autolaunching of a bus
      and checks if it is connectible.
      In build the test is moved from "only non-windows with have_dbus_daemon"
      to "anywhere".
      This is intentional: actually it doesn't execute any external
      binaries on unix (so doesn't require dbus_daemon)
      and now has win32 implementation.
      The test has some problems that are not problems of test itself,
      but are reasoned by current win32 implementation:
       - since the implementation uses global win32 kernel objects
      with fixed names not depending on g_get_user_runtime_dir or other context
      if preexisting bus running by some other libgio-using application
      the test would silently pass.
       - since the implementation uses problematic time-based synchronization,
      that has a race condition between opening and reading mmaped address,
      the test may randomly fail (I'd not seen this in practice).
       - since the implementation autolaunched process works for 3 seconds
      after last client disconnects, the executed subprocess runs for 3 seconds
      after test exit, maybe locking the libgio-2.0-0.dll file for that time.
    • Vasily Galkin's avatar
      gdbus, tests: rename gdbus-unix-addresses test to gdbus-address-get-session · b1f7c22a
      Vasily Galkin authored
      In preparation of adding non-unix testcase to the test.
  15. 08 Mar, 2019 3 commits
  16. 07 Mar, 2019 3 commits
  17. 06 Mar, 2019 1 commit
    • Tomasz Miąsko's avatar
      tests: Fix data race in task test · 330f8999
      Tomasz Miąsko authored
      Ensure that all tasks have already completed before accessing buf array
      from main thread to avoid conflicting data access from multiple threads.
  18. 05 Mar, 2019 2 commits
  19. 04 Mar, 2019 1 commit
  20. 27 Feb, 2019 2 commits
  21. 25 Feb, 2019 1 commit
  22. 21 Feb, 2019 1 commit