1. 06 Jan, 2019 1 commit
  2. 14 Dec, 2018 8 commits
  3. 13 Dec, 2018 3 commits
  4. 11 Dec, 2018 6 commits
  5. 06 Dec, 2018 1 commit
    • Ralf Habacker's avatar
      Skip server oom wildcard test on Windows to avoid firewall exception request · 0f5f95ab
      Ralf Habacker authored
      After starting the test on Windows 10, whether the local user is an
      administrator or not, a dialog box appears with a warning that some
      features of the app have been blocked by the firewall and prompts for
      credentials for an administrator account while the test continues to
      run and pass.
      
      If this request is aborted, the dialog disappears; no restrictions are
      visible for the test case. When the test is restarted, the dialog is also
      no longer displayed.
      
      In the firewall configuration you can then see that test-server-oom.exe
      has been added (but not enabled) for public networks, although no
      confirmation has been received from an administrator account.
      0f5f95ab
  6. 05 Dec, 2018 3 commits
    • Simon McVittie's avatar
      sysdeps test: Wait for spawned process to exit · 7db89148
      Simon McVittie authored
      On Windows, the "out" parameter for the process handle isn't set
      unless we specify G_SPAWN_FLAGS_DO_NOT_REAP_CHILD. That means we
      can't terminate it, and the child process is leaked. When running the
      test individually, the leaked process is harmless apart from its
      resource cost, but when running under CTest, it holds a file descriptor
      open (or something) which causes CTest to not exit.
      
      If we *do* specify G_SPAWN_FLAGS_DO_NOT_REAP_CHILD, we become
      responsible for "reaping" the child process by waiting for its exit
      status, which is an OS-specific action.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
      Resolves: #238
      7db89148
    • Simon McVittie's avatar
      syslog test: Don't assert that we see plain LF newlines · 815fc621
      Simon McVittie authored
      In at least some build configurations that target Windows, we see CRLF
      newlines in the stderr of the subprocess. Leave the newlines unspecified
      and let "*" match them.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
      Resolves: #243
      815fc621
    • Ralf Habacker's avatar
      Fix test-shutdown bail out on Windows · 83bdfea8
      Ralf Habacker authored
      test-shutdown expects a GUID in the bus address by default,
      which is not available under Windows, because on this platform
      an autolaunch address is provided by dbus-run-session and is
      not returned by dbus-daemon.
      
      Bug: !59Reviewed-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
      83bdfea8
  7. 04 Dec, 2018 1 commit
  8. 03 Dec, 2018 2 commits
    • Simon McVittie's avatar
      Translate Python-based tests to C · 1191262f
      Simon McVittie authored
      This simplifies bootstrapping: now you don't have to build dbus,
      build dbus-python (with GLib), and use dbus-python to test dbus.
      
      It also avoids test failures when using facilities like
      AddressSanitizer. When libdbus is built with AddressSanitizer, but the
      system copies of Python and dbus-python were not, dbus-python will exit
      the Python interpreter on load, because libasan wasn't already
      initialized. The simplest way to avoid this is to not use Python:
      the scripts are not *that* hard to translate into C.
      
      Both of these tests happen to be conditionally compiled for Unix only.
      test_activation_forking() relies on code in TestSuiteForkingEchoService
      that calls fork(), which can only work on Unix; meanwhile,
      test_system_signals() tests the system bus configuration, which is
      only relevant to Unix because we don't support using dbus-daemon as
      a privilege boundary on Windows (and in any case D-Bus is not a Windows
      OS feature, so the system bus cannot be used to communicate with OS
      services like it can on most Linux systems).
      
      This is also a partial solution to
      <dbus/dbus#135>, by reducing the
      size of name-test/.
      
      For this to work, we need to build the test-service helper executable
      even if embedded tests are disabled.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
      1191262f
    • Simon McVittie's avatar
      test-service: Write diagnostics to stderr · ebe57443
      Simon McVittie authored
      When run by a TAP test, stdout is reserved for machine-readable
      TAP output.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
      ebe57443
  9. 29 Nov, 2018 1 commit
  10. 20 Nov, 2018 2 commits
  11. 19 Nov, 2018 2 commits
  12. 31 Oct, 2018 7 commits
  13. 23 Oct, 2018 1 commit
    • Simon McVittie's avatar
      dbus-daemon test: Allow much longer for pending fd timeout · 20e6eb7c
      Simon McVittie authored
      The timeout we're using here is 0.5s (500ms), but the actual time taken
      is unbounded, because the OS scheduler might not schedule our process
      for an arbitrary length of time after we become runnable.
      
      We previously allowed up to 1 second, but in the CI jobs for !9
      and !18 we've seen this take up to 3.4 seconds (presumably
      because other tests, or other jobs running on the same shared
      infrastructure, starved this process). Allow up to 10 seconds to guard
      against spurious failures.
      
      The timeout used in the production system.conf is 150 seconds (2½
      minutes), and we're only using the shorter 500ms timeout here to make
      the test complete more quickly, so ±10 seconds is relatively
      insignificant: the main thing is that it's finite.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
      20e6eb7c
  14. 19 Oct, 2018 2 commits