← Back to team overview

touch-packages team mailing list archive

[Bug 1441796] Re: Harness constantly prints boost::filesystem errors and sometimes aborts

 

Any chance of a stack trace? That would be really useful. How can I
reproduce this?

Looking at the code, I think the issue here may be that the registry is
running in a non-standard location and there is no unity-scopes
directory under .local/share (or .local/share itself doesn't exist).

Pawel ran into something similar yesterday when running in a chroot. I
think I have a fair idea of what's going on, but would still appreciate
a stack trace, if possible. In particular, I'm interested in termination
due to the uncaught exception. That clearly is a bug in our code but,
without a stack trace, it might be difficult to identify the exact
source.

I'll see what I can learn from the code.

** Changed in: unity-scopes-shell (Ubuntu)
     Assignee: (unassigned) => Michi Henning (michihenning)

** Changed in: unity-scopes-shell (Ubuntu)
       Status: Triaged => In Progress

-- 
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


References