Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 887
    • Issues 887
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 49
    • Merge requests 49
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • GLib
  • Issues
  • #2206

Closed
Open
Created Sep 15, 2020 by Simon McVittie@smcvDeveloper

Intermittent gdbus-server-auth TCP test failures with 2.66.0

Steps to reproduce

  • Build the Debian 2.66.0-1 package on many architectures. (This includes !1641 (merged).)

Expected result

Tests pass consistently

Actual result

On amd64 (x86_64), once out of 2 attempts, and on armhf (ARMv7 EABI hardfloat 32-bit little-endian), twice out of 3 attempts, the gdbus-server-auth test failed in /gdbus/server-auth/tcp.

In each of the three failing logs, /gdbus/server-auth and /gdbus/server-auth/abstract pass. On entering /gdbus/server-auth/tcp, we successfully set up the GDBus TCP server, successfully connect a GDBus client to it using DBUS_COOKIE_SHA1 authentication, but then fail at the first of 20 trials connecting a libdbus client to test interoperability.

This is from one of the ARM logs. The other ARM log and the x86_64 log look very similar.

# GLib-DEBUG: g_set_user_dirs: Setting HOME to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/home
# GLib-DEBUG: g_set_user_dirs: Setting XDG_CACHE_HOME to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/cache
# GLib-DEBUG: g_set_user_dirs: Setting XDG_CONFIG_DIRS to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/system-config1:/tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/system-config2
# GLib-DEBUG: g_set_user_dirs: Setting XDG_CONFIG_HOME to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/config
# GLib-DEBUG: g_set_user_dirs: Setting XDG_DATA_DIRS to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/system-data1:/tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/system-data2
# GLib-DEBUG: g_set_user_dirs: Setting XDG_DATA_HOME to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/data
# GLib-DEBUG: g_set_user_dirs: Setting XDG_RUNTIME_DIR to /tmp/test_gdbus-server-auth_P7MQQ0/gdbus/server-auth/tcp/.dirs/runtime
# Testing GDBus server at tcp:host=127.0.0.1 / libdbus client, with flags: external:false anonymous:false sha1:false abstract:false tcp:true
# Connectable address: tcp:host=127.0.0.1,port=36001
# GLib-GIO-DEBUG: Accepting "ANONYMOUS" authentication
# GLib-GIO-DEBUG: Accepting "DBUS_COOKIE_SHA1" authentication
# GLib-GIO-DEBUG: Accepting "EXTERNAL" authentication
# GLib-GIO-DEBUG: Authorizing peer with credentials: GCredentials:linux-ucred:pid=0
# GLib-GIO-DEBUG: New connection from peer with credentials: GCredentials:linux-ucred:pid=0
# GLib-GIO-DEBUG: Server says GDBus client is uid 4294967295, pid -1
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
**
GLib-GIO:ERROR:../../../gio/tests/gdbus-server-auth.c:416:do_test_server_auth: assertion failed (libdbus_call.error.name == NULL): ("org.freedesktop.DBus.Error.Failed" == NULL)
Bail out! GLib-GIO:ERROR:../../../gio/tests/gdbus-server-auth.c:416:do_test_server_auth: assertion failed (libdbus_call.error.name == NULL): ("org.freedesktop.DBus.Error.Failed" == NULL)

Unfortunately we don't have timing information, G_DBUS_DEBUG or DBUS_VERBOSE available for this.

Assignee
Assign to
Time tracking