touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

I believe the linked branch should fix this. Could you give it a spin
please?

I still would very much appreciate seeing a stack trace, particularly
for the terminate() problem.

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

Title:
  Harness constantly prints boost::filesystem errors and sometimes
  aborts

Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  terminate called after throwing an instance of 'boost::filesystem::filesystem_error'
    what():  boost::filesystem::equivalent: No such file or directory: "/tmp/tmpvb08fgci/.local/share/unity-scopes/unconfined/client/logs", "/tmp/tmp9ha9gfc6/.local/share/unity-scopes/unconfined/client/logs"
  scoperegistry: no remote registry configured, only local scopes will be available
  Aborted

  When running the tests locally, many similar messages to this are
  repeated, but often without aborting. On the jenkins armhf builder, it
  seems to cause an abort fairly consistently, due to this unhandled
  exception. This also causes the python3 process to hang, which causes
  further errors to show up in the logs, as the chroot apparently cannot
  unmount /run/shm when this happens.

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