2015-08-24 12:17:31 -04:00
|
|
|
[tox]
|
2022-04-12 12:35:48 -04:00
|
|
|
envlist = py37, py38, py39, py310
|
2021-04-08 07:09:48 -04:00
|
|
|
|
|
|
|
# we require tox>=2.3.2 for the fix to https://github.com/tox-dev/tox/issues/208
|
|
|
|
minversion = 2.3.2
|
2015-08-24 12:17:31 -04:00
|
|
|
|
2022-02-17 10:55:14 -05:00
|
|
|
# the tox-venv plugin makes tox use python's built-in `venv` module rather than
|
|
|
|
# the legacy `virtualenv` tool. `virtualenv` embeds its own `pip`, `setuptools`,
|
|
|
|
# etc, and ends up being rather unreliable.
|
|
|
|
requires = tox-venv
|
|
|
|
|
2018-08-13 02:47:46 -04:00
|
|
|
[base]
|
2015-08-24 12:17:31 -04:00
|
|
|
deps =
|
2015-11-13 11:22:51 -05:00
|
|
|
python-subunit
|
|
|
|
junitxml
|
2018-11-28 04:59:31 -05:00
|
|
|
coverage
|
2020-12-17 17:58:00 -05:00
|
|
|
|
|
|
|
# this is pinned since it's a bit of an obscure package.
|
|
|
|
coverage-enable-subprocess==1.0
|
2016-12-06 06:35:14 -05:00
|
|
|
|
2018-10-30 17:00:31 -04:00
|
|
|
# cyptography 2.2 requires setuptools >= 18.5
|
|
|
|
#
|
|
|
|
# older versions of virtualenv (?) give us a virtualenv with the same
|
|
|
|
# version of setuptools as is installed on the system python (and tox runs
|
|
|
|
# virtualenv under python3, so we get the version of setuptools that is
|
|
|
|
# installed on that).
|
|
|
|
#
|
|
|
|
# anyway, make sure that we have a recent enough setuptools.
|
2021-04-27 08:13:07 -04:00
|
|
|
setuptools>=18.5
|
2018-10-30 17:00:31 -04:00
|
|
|
|
|
|
|
# we also need a semi-recent version of pip, because old ones fail to
|
|
|
|
# install the "enum34" dependency of cryptography.
|
2021-04-27 08:13:07 -04:00
|
|
|
pip>=10
|
2018-10-30 17:00:31 -04:00
|
|
|
|
2021-01-07 06:41:54 -05:00
|
|
|
# default settings for all tox environments
|
2018-08-13 02:47:46 -04:00
|
|
|
[testenv]
|
|
|
|
deps =
|
|
|
|
{[base]deps}
|
2021-01-07 06:41:54 -05:00
|
|
|
extras =
|
|
|
|
# install the optional dependendencies for tox environments without
|
|
|
|
# '-noextras' in their name
|
2021-04-08 07:09:48 -04:00
|
|
|
# (this requires tox 3)
|
2021-01-07 06:41:54 -05:00
|
|
|
!noextras: all
|
|
|
|
test
|
2018-08-13 02:47:46 -04:00
|
|
|
|
|
|
|
setenv =
|
2020-12-17 17:58:00 -05:00
|
|
|
# use a postgres db for tox environments with "-postgres" in the name
|
|
|
|
# (see https://tox.readthedocs.io/en/3.20.1/config.html#factors-and-factor-conditional-settings)
|
2019-02-20 02:42:24 -05:00
|
|
|
postgres: SYNAPSE_POSTGRES = 1
|
2020-12-17 17:58:00 -05:00
|
|
|
|
|
|
|
# this is used by .coveragerc to refer to the top of our tree.
|
2019-08-29 08:19:57 -04:00
|
|
|
TOP={toxinidir}
|
2018-08-13 02:47:46 -04:00
|
|
|
|
|
|
|
passenv = *
|
|
|
|
|
2015-08-24 12:17:31 -04:00
|
|
|
commands =
|
2020-12-17 17:58:00 -05:00
|
|
|
# the "env" invocation enables coverage checking for sub-processes. This is
|
|
|
|
# particularly important when running trial with `-j`, since that will make
|
|
|
|
# it run tests in a subprocess, whose coverage would otherwise not be
|
|
|
|
# tracked. (It also makes an explicit `coverage run` command redundant.)
|
|
|
|
#
|
|
|
|
# (See https://coverage.readthedocs.io/en/coverage-5.3/subprocess.html.
|
|
|
|
# Note that the `coverage.process_startup()` call is done by
|
|
|
|
# `coverage-enable-subprocess`.)
|
|
|
|
#
|
|
|
|
# we use "env" rather than putting a value in `setenv` so that it is not
|
|
|
|
# inherited by other tox environments.
|
|
|
|
#
|
|
|
|
/usr/bin/env COVERAGE_PROCESS_START={toxinidir}/.coveragerc "{envbindir}/trial" {env:TRIAL_FLAGS:} {posargs:tests} {env:TOXSUFFIX:}
|
2015-08-24 12:17:31 -04:00
|
|
|
|
2017-09-05 11:35:23 -04:00
|
|
|
# As of twisted 16.4, trial tries to import the tests as a package (previously
|
|
|
|
# it loaded the files explicitly), which means they need to be on the
|
|
|
|
# pythonpath. Our sdist doesn't include the 'tests' package, so normally it
|
|
|
|
# doesn't work within the tox virtualenv.
|
|
|
|
#
|
|
|
|
# As a workaround, we tell tox to do install with 'pip -e', which just
|
|
|
|
# creates a symlink to the project directory instead of unpacking the sdist.
|
|
|
|
#
|
|
|
|
# (An alternative to this would be to set PYTHONPATH to include the project
|
|
|
|
# directory. Note two problems with this:
|
|
|
|
#
|
|
|
|
# - if you set it via `setenv`, then it is also set during the 'install'
|
|
|
|
# phase, which inhibits unpacking the sdist, so the virtualenv isn't
|
|
|
|
# useful for anything else without setting PYTHONPATH similarly.
|
|
|
|
#
|
|
|
|
# - `synapse` is also loaded from PYTHONPATH so even if you only set
|
|
|
|
# PYTHONPATH for the test phase, we're still running the tests against
|
|
|
|
# the working copy rather than the contents of the sdist. So frankly
|
|
|
|
# you might as well use -e in the first place.
|
|
|
|
#
|
|
|
|
# )
|
|
|
|
usedevelop=true
|
|
|
|
|
2018-09-27 09:21:54 -04:00
|
|
|
|
2019-03-18 13:45:45 -04:00
|
|
|
|
2019-12-03 04:21:25 -05:00
|
|
|
[testenv:benchmark]
|
|
|
|
deps =
|
|
|
|
{[base]deps}
|
|
|
|
pyperf
|
|
|
|
setenv =
|
|
|
|
SYNAPSE_POSTGRES = 1
|
|
|
|
commands =
|
|
|
|
python -m synmark {posargs:}
|
|
|
|
|