← Back to team overview

touch-packages team mailing list archive

[Bug 1360919] Re: Registry test fails when coverage enabled

 

** Changed in: unity-scopes-api (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  Registry test fails when coverage enabled

Status in “unity-scopes-api” package in Ubuntu:
  Fix Released

Bug description:
  As of revision 451, the Registry test fails, but only when compiled
  with coverage. The rename in the manually_started_scope test (and
  following tests) fails with

  RegistryObject::ScopeProcess: Manually started process for scope: "testscopeC" exited
  unknown file: Failure
  C++ exception with description "boost::filesystem::rename: Directory not empty: "/home/michi/src/fix-reaper-test/build/test/gtest/scopes/Registry/scopes/testscopeC", "/home/michi/src/fix-reaper-test/build/test/gtest/scopes/Registry/other_scopes/testscopeC"" thrown in the test body.

  Presumably, that's because, with coverage, the .gcda file gets written
  into the scope's directory, and filesystem::rename throws if a
  directory is moved that isn't empty.

  Not sure how to best fix this yet. -fprofile-dir might help.

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