Fix lookup scoping multi-match ordering

When look-up is occurring the possible provider
ordering is used instead of the scope returned provider
ordering. This causes incorrect matches when look-up
argument names that are produced by multiple providers (at
the same scope level) all providing the same requirement
name.

The scope order should be enforced as the de-facto order
and not the order that the storage unit finds (which is
hash based and varies depending on hash ordering).

Closes-Bug: #1425326

Change-Id: I15f1ee5515758bdc470c0f7dd7a2f616923e5628

1 files changed, 7 insertions, 0 deletions

diff --git a/taskflow/tests/utils.py b/taskflow/tests/utils.py
index 9e6e2a3..031dd70 100644
--- a/taskflow/tests/utils.py
+++ b/taskflow/tests/utils.py
@@ -89,6 +89,13 @@ class DummyTask(task.Task):
         pass
 
 
+class AddOne(task.Task):
+    default_provides = 'result'
+
+    def execute(self, source):
+        return source + 1
+
+
 class FakeTask(object):
 
     def execute(self, **kwargs):