New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Assigned
Owner:
User never visited
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment
ap-demons unit test failing with dbus errors on several canaries
Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 6 (6 days ago) Back to list
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of rspangler@google.com

ap-daemons-0.0.3-r3593: [ RUN      ] GcdCommandsStateTest.ConfigureBridgeModeState
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:bus.cc(427)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:shill_connection.h(320)] Unable to connect to signal: PropertyChanged on interface: org.chromium.flimflam.Manager
ap-daemons-0.0.3-r3593: [1206/112453:INFO:netmgr_client_shill.cc(90)] NetMgrClientShill ctor
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:bus.cc(427)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:dbus_method_invoker.h(117)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.Failed, Message=Failed to call D-Bus method: org.chromium.flimflam.Manager.GetProperties
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:bus.cc(427)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:dbus_method_invoker.h(117)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.Failed, Message=Failed to call D-Bus method: org.chromium.flimflam.Manager.GetProperties
ap-daemons-0.0.3-r3593: [1206/112453:ERROR:bus.cc(427)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

Builders failed on: 
- arkham-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/arkham-release/1738
- gale-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/gale-release/1846
- whirlwind-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/whirlwind-release/2467


 
Comment 1 by rspangler@chromium.org, Dec 6 (6 days ago)
Cc: -rspangler@google.com rspangler@chromium.org shamanthakumar@chromium.org
Owner: jintao@chromium.org
Status: Assigned
May be related to issue 763152?  Can you route to the right owner?
Comment 2 by jintao@google.com, Dec 6 (6 days ago)
The ERROR log attached in the ticket is actually benign. The actual builder failure is caused by the unit test failure

ap-daemons-0.0.3-r3593: [  FAILED  ] MeshManagerTest.FailsOnInvalidState

Assigning to nshai@, owner of this unit test 
Comment 3 by jintao@chromium.org, Dec 6 (6 days ago)
Owner: nshai@chromium.org
Comment 4 by nshai@google.com, Dec 6 (6 days ago)
Putting a fix into the branch now.
Comment 5 by gogerald@chromium.org, Dec 6 (6 days ago)
Labels: -Sheriff-Chromium
remove 'Sheriff-Chromium',
Sign in to add a comment