delta/openstack/taskflow.git/taskflow/tests/unit/test_utils.py, branch master

Remove six

2022-05-18T07:12:37+00:00

This library no longer supports Python 2, thus usage of six can be
removed. This also removes workaround about pickle library used in
Python 2 only.

Change-Id: I19d298cf0f402d65f0b142dea0bf35cf992332a9

Replace assertEqual(None, *) with assertIsNone in tests

2016-07-12T03:46:19+00:00

Replace assertEqual(None, *) with assertIsNone in tests to have more
clear messages in case of failure.

Change-Id: I74452af6d840bcf612fd3bb2521db9134460dd63
Closes-Bug: #1280522

Allow for alterations in decider 'area of influence'

2016-01-10T06:42:17+00:00

Christmas came early.

Closes-Bug: #1479466

Change-Id: I931d826690c925f022dbfffe9afb7bf41345b1d0

Change name of misc.ensure_dict to misc.safe_copy_dict

2015-12-15T00:18:11+00:00

Change-Id: I2ff3b9bb4d0b8143163e4bf370f10c74e79dbd31

Add optional 'defer_reverts' behavior

2015-11-18T01:03:41+00:00

This makes it possible to REVERT a subflow
and have it also revert the parent flow if
the parent flow doesn't have its own retry
strategy. We will probably want to make this
new behavior the default or only behavior
in a future release.

Change-Id: Iea5ac366380ba7396a87d0185703549fb0c2f825

Fix order of assertEqual for unit.test_*

2015-10-18T01:42:49+00:00

First parameter should be the expected value.

Change-Id: I2941296e38c3245da298cc64aeb5636fbc4b2eb6
Partial-Bug: #1357117

Small refactoring of 'merge_uri' utility function

2015-05-02T17:31:40+00:00

Perform some small adjustments/cleanups and add some
unit tests to ensure this function keeps operating as
expected.

Change-Id: I496bd6844072f57624de31fc7ddb0362f163cc53

Merge "Added a map and a reduce task"

2015-03-14T04:56:30+00:00

Added a map and a reduce task

2015-03-12T19:22:06+00:00

- Added a MapFunctorTask and ReduceFunctorTask to mimic the python
  builtin functions map and reduce, respectively

Change-Id: I29cd1249e1671aedfd2d25460d746b8d2154df2b

Fix lookup scoping multi-match ordering

2015-02-25T06:34:14+00:00

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