While it'd be technically more correct to split these out into dev
requirements, I think a little bit of an overhaul of our bootstrap
process overdue. We can save that work for then. For now, this smooths
a kink in the docker-compose work we're doing.
Signed-off-by: Zack Cerza <zack@redhat.com>
cryptography>=2.7
nose
pip-tools
-pytest==3.7.1
+pytest
+mock
requests
tox
xmltodict
# This file is autogenerated by pip-compile with python 3.9
# To update, run:
#
-# pip-compile --output-file=- requirements.in
+# pip-compile requirements.in
#
ansible==2.9.24
# via teuthology
# via openstacksdk
argparse==1.4.0
# via teuthology
-atomicwrites==1.4.0
- # via pytest
attrs==21.2.0
# via
# cmd2
# via teuthology
idna==3.2
# via requests
+iniconfig==1.1.1
+ # via pytest
ipy==1.1
# via teuthology
iso8601==0.1.16
# via teuthology
markupsafe==2.0.1
# via jinja2
-more-itertools==8.8.0
- # via pytest
+mock==4.0.3
+ # via teuthology
msgpack==1.0.2
# via oslo.serialization
munch==2.5.0
packaging==21.0
# via
# oslo.utils
+ # pytest
# tox
paramiko==2.7.2
# via teuthology
# munch
# oslo.i18n
# pyopenssl
- # pytest
# python-dateutil
# python-keystoneclient
# tox
toml==0.10.2
# via
# teuthology
+ # pytest
# tox
tomli==1.2.1
# via pep517
passenv = HOME
deps=
-r{toxinidir}/requirements.txt
- mock==2.0.0
pytest-cov==2.8.1
coverage==4.5.4
log_format = %(asctime)s %(levelname)s %(message)s
-r{toxinidir}/requirements.txt
sphinx
sphinxcontrib-programoutput
- mock==2.0.0
commands=
sphinx-apidoc -f -o . ../teuthology ../teuthology/test ../teuthology/orchestra/test ../teuthology/task/test
sphinx-build -b html -d {envtmpdir}/doctrees . {envtmpdir}/html
sitepackages=True
deps=
-r{toxinidir}/requirements.txt
- mock==2.0.0
commands=py.test -v {posargs:teuthology/openstack/test/test_openstack.py}
basepython=python3
basepython=python3
deps=
-r{toxinidir}/requirements.txt
- mock==2.0.0
commands=
py.test -v {posargs} teuthology/openstack/test/openstack-integration.py