touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

Public bug reported:

Just had a failure on Arm on Jenkins. It looks like we are emitting two
"uninstalled" events in some cases, even though only one scope is
removed. This is reproducable locally.

There is also an issue around install. Locally, we get one event for
testscopeC being installed but, on Jenkins, the trace shows two events.
In turn, the test doesn't expect that.

Something is fishy here, and it looks like the ScopesWatcher could do
with some refactoring.

Console log attached. Line numbers are consistent with r531 of devel.

** Affects: unity-scopes-api (Ubuntu)
     Importance: High
     Assignee: Michi Henning (michihenning)
         Status: Confirmed

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => High

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

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

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

Title:
  ScopesWatcher behavior doesn't agree with Registry test

Status in “unity-scopes-api” package in Ubuntu:
  Confirmed

Bug description:
  Just had a failure on Arm on Jenkins. It looks like we are emitting
  two "uninstalled" events in some cases, even though only one scope is
  removed. This is reproducable locally.

  There is also an issue around install. Locally, we get one event for
  testscopeC being installed but, on Jenkins, the trace shows two
  events. In turn, the test doesn't expect that.

  Something is fishy here, and it looks like the ScopesWatcher could do
  with some refactoring.

  Console log attached. Line numbers are consistent with r531 of devel.

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