touch-packages team mailing list archive

[Rodney Dawes <1441796@xxxxxxxxxxxxxxxxxx>]

As the branch was targeted and landed in /devel, I haven't been able to
properly test it (as the failure is only happening in Jenkins), but
given that the failure is about the logs directory missing, and the
branch creates them, I'm confident it will solve the problem. It just
needs to get into the archive that CI builds against, to be usable
there, and unblock my branch (though due to final freeze, I expect it to
be blocked a bit longer now anyway).

On Thu, 2015-04-16 at 08:47 +0000, Michi Henning wrote:
> Rodney, did the branch fix the problem for you?
>

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