Comment 1 for bug 1267026

Affecting also unity-scopes-api as it seems to be a race coming from there.

What happens in this test is that we setup a custom registry with a single scope in its scope directory and call registry->list(). For some reason the registry sometimes returns 0 entries, although one scope should always be present.

A bit more info - this seems to happen only when armhf build is being slow, plus the failure is happening already in tests' setup function (the one that is run for each test) *but* it fails only on the first test - ie right after spawning the registry, further tests that are using the exact same test setup function do not fail on the same check.

From this it would appear that if list() is called too early, it might not have information about the local scopes yet, and therefore sends back an empty response to the client.