touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #35100
[Bug 1394080] Re: ScopesWatcher behavior doesn't agree with Registry test
So as discussed on IRC, the problem appears to be that, for a single
copy/move of a file, we get two notifications from the ScopesWatcher,
which causes the wait_for_update() at Registry_test.cpp:531 to return
prematurely.
--
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
References