| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Change-Id: Ia2a7fb48ca36ce9354ac47060c3a16be15da80a7
|
|
|
|
| |
Change-Id: Id5908ac0ea4300f8b0eb660c107cfcf0452e6490
|
|
|
|
| |
Change-Id: I9bbf5d9082e4e6ee9283c7e11ed0b2474a4e070a
|
|
|
|
| |
Change-Id: Ide0e95f47a88015801e445c1cd659f30c51e0c0b
|
|
|
|
| |
Change-Id: I3af87566b255957c273a8b9f392425877394ce8a
|
|
|
|
| |
Change-Id: I027659520dad2166b8e28ec0a2334cd58c563dfc
|
|
|
|
| |
Change-Id: Ida3d96383c54ff6b16297f5bfc46804dc954bc59
|
|
|
|
| |
Change-Id: I39c4858101f83a269a3a0b2f1c49497eb4768001
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The requirement for PyMySQL got merged into the requirements
repo, so now instead of just testing sqlite (or postgres) in py3.x
we can now test against the mysql instance that should exist in the
test environments (just like we test with MySQL-python in py2.x).
Change-Id: I6e48df78d20389d65de8210c6157abb99f52d7dd
|
|/
|
|
| |
Change-Id: Ic0d84da1e3f06679be20973c8f618f561a76971d
|
|
|
|
| |
Change-Id: I48350d765a1345a98de07bc1e269940b849840b1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The oslotest library has a nice openstack testing integrated
base class that can ensure we setup our base test case using
the right logging fixtures, test timeouts, and output fixtures
that better operate in the openstack ecosystem.
This will also allow us to remove some of the functionality
that we currently have in our base test case and replace it with
the equivalent (or better) functionality that oslotest now
provides.
Part of blueprint use-oslo-test
Change-Id: I1602d5180ec8649a1899185972750ddddf65990f
|
|
|
|
|
|
|
|
|
|
|
| |
This change removes the need for an optional-requirements
file which isn't being kept up to date with the rest of the
openstack ecosystem and moves most of the customizations to
test-requirements and where different versions are still
needed (aka for SQLAlchemy) we place those varations into
there needed tox environment as required.
Change-Id: I443794b83de3f6a196fa7fc29a90620fb51b7f4c
|
|
|
|
| |
Change-Id: I966ff8ba796774c6ebf5b99ae799bb14196fcf81
|
|
|
|
|
|
|
| |
Co-authored-by: Joshua Harlow <harlowja@gmail.com>
Addresses-Bug: #1365061
Change-Id: I64ae9191863564e278a35d42ec9cd743a233028e
|
|
|
|
| |
Change-Id: Ifeed3788115e8fca7f9a23c293f7d91118743824
|
|
|
|
| |
Change-Id: I4758cb3c316356299595ca895e13cfcfc0b88123
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ia8272ed8086d13fe1f1853e6cff768e9b75a2793
|
|/
|
|
| |
Change-Id: I7e075ff2afeb380f28ae1800bbb91389b772c598
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update hacking to the new requirements version and
fix about half of the new reported issues. The other
hacking issues are for now ignored until fixed by
adjusting our tox.ini file.
This commit fixes the following new hacking errors:
H405 - multi line docstring summary not separated
with an empty line
E265 - block comment should start with '# '
F402 - import 'endpoint' from line 21 shadowed by
loop variable
Change-Id: I6bae61591fb988cc17fa79e21cb5f1508d22781c
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Bump up the sphinx requirement to match the
openstack requirements version to ensure
consistency among projects.
Change-Id: Ia348566c1c22ca31fa1cbdeb38d902ca0f622378
|
|/
|
|
|
|
|
|
|
|
| |
Zake has been updated in the global requirements
repository to be zake>=0.0.20, so in order for the
requirements bot to get its change through (without
updating hacking) we need to separate this change
out.
Change-Id: I5cf4407104409785fe4ee746af9fed7b766474e4
|
|
|
|
|
|
|
| |
Since I63c6159eb23430a181eb20016b35366c2fbbf9f8 got merge we have
to update sphinx version, too.
Change-Id: Ic25b361fd34ee7df7010bc60c1ff44d3b8892a6c
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of using the zake provided flush method (which
does have issues, since it does not guarantee that the
associated watches will have been called) instead use a
new method which creates nodes, waits for there watches
to be triggered, does other work, and then deletes the
node and waits for that watcher to be triggered; this is
more stable (as it depends on the linearity guarantee
of zookeeper and the kazoo threading model).
Change-Id: I12fd9c7bcc5cd9009b4175166edfc924e94161bf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Retain the posting order by using sequencing when posting
jobs to a jobboard (at least in the impl_zookeeper case
this is possible).
Adjust the interface to recommend that jobboard implementations
post in oldest to newest order (we can not easily enforce this
since some implementations will likely not be able to do this
in every scenario).
Bring in a new zake which has sequencing support (since this
is required to support this feature).
Change-Id: I0c475c3c1d16e9bbc9db6ff0ad6b7103c5948a47
|
|
|
|
| |
Change-Id: I37a5bf7f06760e99c075da87a7917a358ad9bc7d
|
|
|
|
|
|
|
|
|
|
| |
- move all docs sources to docs/source;
- rework documentation structure and contents;
- update conf.py and clean it up;
- switch use oslosphinx;
- add sphinx and oslosphinx to test requrements.
Change-Id: Ied37f86e559516ef7a106e2870d4817ff01a8af4
|
|
|
|
|
|
|
|
|
| |
Kazoo is an optional dependency of taskflow: it is required when
zookeeper persistence layer or if kazoo_utils are used. So we should
move it to where these type of optional requirements are currently
placed.
Change-Id: I9d1605af266f4a79fd6ebfee2d68a4f4f7413022
|
|
|
|
|
|
|
|
|
|
| |
The problem of incompatibility between subunit<0.0.18 and
testtools>=0.9.35 was fixed in subunit>=0.0.18:
https://launchpad.net/subunit/trunk/0.0.18
Additionally, subunit is now depends on testtools>=0.9.34
Change-Id: If74785f9d9a59a9d6dc534b02f25ad041ee777cb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Only use zake in unit-tests by providing a client
to the backend as a fake client. This avoids cases
where a real client should be provided; and if not
provided then a error should be thrown. This avoids
potential misuse of zake (which really is only designed
for testing usage and not for actual usage in production).
- Add a kazoo_utils file that will be shared to make
kazoo clients and to parse hosts into a kazoo friendly
format for other usages of kazoo clients that will be
appearing soon.
- Ensure basic assertions when creating the zk backend,
don't allow empty paths, require absolute paths.
- Update exc_wrapper to have slightly more descriptive
messages that identify more of what the original errors
category was.
- Create initial paths on upgrade() to mirror what other
backends are doing in their upgrade() function. Other
backends do their initial steps to upgrade there backends
in this function (ie sqlalchemy does its migrations here
so it seems to be consistent place to make sure zookeeper
paths are created correctly).
Change-Id: Iabafe73c059b4719617f01bd1ee35795f71ca21d
|
|
|
|
|
|
|
| |
SubUnit is incompatible with newer testtools.
Closes-bug: 1274050
Change-Id: Ibe855930cecf6598ea72c13f609116450c719b46
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test cases are in taskflow/tests/unit/persistence/test_zk_persistence
and taskflow/tests/unit/persistence/test_zake_persistence. The former
requires a working ZooKeeper cluster, and the latter uses a fake
in-memory backend. Right now, due to the lack of ZooKeeper in Jenkins,
the former test is disabled. To enable it, simply uncomment the code
and change "hosts" in conf to your ZooKeeper cluster's addresses.
Also moved some shared helper functions from
taskflow/persistence/backends/impl_dir to
taskflow/utils/persistence_utils.
Implements: blueprint zk-logbook
Change-Id: Ia1b7ef8312a1761515515fd206b36be135119737
|
|
|
|
|
|
|
| |
- sync requirements with global openstack requirements;
- fix flake8 errors.
Change-Id: I7430367726708787fc068e18506fbbb117d23952
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the python 3.3 testing work by selectively
disabling & including eventlet, switch to testtools
and testrepository which has 2.6, 2.7, 3.2+ unified
testing support so that we can correctly run our
tests in all supported python versions.
Closes-Bug: #1251660
Co-authored-by: Alexander Gorodnev <agorodnev@griddynamics.com>
Change-Id: I23b6f04387cfd3bf6b5a044edffa446ca897ce3a
|
|
|
|
|
|
|
|
|
|
|
| |
Match the requirements for taskflow with
the openstack requirements (note the upstream
requirements are missing 'futures' and 'networkx')
and update the new hacking violations that were
detected due to the hacking requirement version
bump.
Change-Id: I8d1326cf2a8b1ea062f5e9aacd0c4f8261c6531a
|
|
Change-Id: I433711ba417dbb15f616fa488cec389f3138b00a
|