1. 25 Feb, 2019 1 commit
  2. 22 Feb, 2019 4 commits
  3. 21 Feb, 2019 6 commits
    • Philip Withnall's avatar
      Merge branch 'code-owners' into 'master' · 86201989
      Philip Withnall authored
      docs: Populate CODEOWNERS file
      Closes #1668
      See merge request GNOME/glib!684
    • Philip Withnall's avatar
      docs: Populate CODEOWNERS file · f703bed5
      Philip Withnall authored
      Rename it from CODE-OWNERS and make it follow the documented syntax
      supported by GitLab:
      https://docs.gitlab.com/ee/user/project/code_owners.html. Currently our
      version of GitLab doesn’t support it, but it may do in future.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
    • Philip Withnall's avatar
      tests: Unmark socket-service test as flaky · 07414e17
      Philip Withnall authored
      This essentially reverts commit
      The preceding two commits have fixed the test so it’s no longer flaky.
      The following command gives 5000 passes in a row for me:
      meson test -C /opt/gnome/build/glib/ socket-service --repeat 5000
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      Fixes: #1679
    • Philip Withnall's avatar
      tests: Fix unlikely race in socket-service test · f25c3f27
      Philip Withnall authored
      It’s occasionally possible for the cancellation of the service to happen
      before connection_cb() gets scheduled in the other thread. The
      locking/unlocking order of mutex_712570 requires:
       • test_threaded_712570(): lock mutex
       • test_threaded_712570(): start wait loop
       • connection_cb(): lock mutex
       • test_threaded_socket_service_finalize(): unlock mutex
       • test_threaded_712570(): end wait loop
       • test_threaded_712570(): unlock mutex
      Fix that by quitting the main loop once connection_cb() has been called
      (i.e. once the server thread has received the incoming connection
      request), rather than just after the client thread (main thread) has
      sent a connection request.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      Helps: #1679
    • Philip Withnall's avatar
      tests: Fix flaky socket-service test caused by GTask scheduling · 2aea9c84
      Philip Withnall authored
      On about 1 in 3 test runs, the socket-service would fail with the
      ref_count assertion in connection_cb() failing (the ref_count would be 3
      rather than the expected 2).
      This was happening because the GTask from
      g_socket_listener_accept_socket_async() now always takes at least one
      main context iteration to return a result (whereas before
      6f3d57d2 it might have taken zero), but
      the ref_count can drop below 3 before the process of returning a result
      starts. During the process of returning a result, the ref_count
      temporarily increases again, which is what was breaking the test.
      Fix this by waiting for one more main context iteration. This is a bit
      of a hack, but the real fix would be to expose the outstanding_accept
      boolean from GSocketService as public API (which the test can
      interrogate), and that seems too much like exposing internal state.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      Helps: #1679
    • Jordi Mas's avatar
      Update Catalan translation · b1033dd3
      Jordi Mas authored
  4. 20 Feb, 2019 5 commits
  5. 18 Feb, 2019 6 commits
  6. 16 Feb, 2019 2 commits
  7. 14 Feb, 2019 9 commits
  8. 13 Feb, 2019 7 commits