touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

We haven't seen this again in many months. Possibly, it was a hopelessly
overloaded builder. Closing as invalid.

** Changed in: unity-scopes-api (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1362367

Title:
  system() fails in RegistryObject

Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  if (safe_system_call(started_message) != 0)

  This fails non-deterministically in the Registry test, even though it
  shouldn't.

  I suspect the lack of thread safety of system() is to blame, and the
  safe_system_call() method with its lock doesn't do the job we were
  hoping it would.

  I don't think we can rely on system() to do anything for us. (I've had
  problems in the past where it would hang occasionally, for example.)

  Forking a shell is also a supremely expensive way to send a single
  dbus message. It probably would be better for us to cobble our own
  dbus message together. But do we have a thread-safe dbus API?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1362367/+subscriptions