ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-19 04:57:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
d641aef2a3
tahoe-lafs/tox.ini

80 lines
2.8 KiB
INI
Raw Normal View History

add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
# Tox (http://tox.testrun.org/) is a tool for running tests
# in multiple virtualenvs. This configuration file will run the
# test suite on all supported python versions. To use it, "pip install tox"
# and then run "tox" from this directory.
[tox]
envlist = py27
[testenv]
passenv = USERPROFILE HOMEDRIVE HOMEPATH
tox.ini: skip default install We use "--deps = --editable=.[test]" to achieve three goals: * make tahoe and it's dependencies available for tests * use --editable, which is faster and allows "coverage run" to get the source filenames right * use the [test] extra, which includes "mock" Tox's default install command does the first, but doesn't use --editable, so when the "deps" stage comes around, there's already a non-editable install in place. It seems to get the [test] extra right, but it doesn't wind up with an editable install. So we disable the default install command and rely on the "deps" clause instead.
2016-05-09 20:56:06 +00:00
# the default install is non-(--editable), and would displace our -e .[test]
skip_install = True
tox.ini: use --editable to work around old-pip bug One of the buildslaves (Ubuntu wily 15.10) has a very old pip-1.5.6, which doesn't know how to "pip install" a filepath+extra (like ".[test]") unless --editable is also used. It's convenient to have --editable set anyways (so you can do subsequent narrow testing without re-running tox, by running ".tox/py27/bin/trial TESTCASE" or use .tox/py27/bin/activate), so changing the dependency from ".[test]" to "--editable=.[test]" is the easiest way to work around that older buildslave. (I could also have upgraded the buildslave to use a newer pip, but 15.10 is pretty recent and other people will probably hit this too, so this way it's fixed for everybody). refs ticket:2776
2016-04-12 21:28:02 +00:00
deps = --editable=.[test]
add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
commands =
tox: add pyflakes, which was accidentally removed from CI
2016-07-20 00:18:31 +00:00
pyflakes src static misc setup.py
tox: run tahoe --version for buildbot, remove update_version Our setup.cfg ensures that 'setup.py update_version' happens early enough. And doing it from tox's commands= is too late anyways (because we aren't using Versioneer, so the _version.py file must be updated before tox installs a static copy into the virtualenv). The buildbot's main run-trial-with-tox command has been updated to scan for the 'tahoe --version' output and include the version string in the buildbot results.
2016-03-18 05:01:33 +00:00
tahoe --version
setup.py: remove 'make_executable' command
2016-03-16 01:19:54 +00:00
trial --rterrors {posargs:allmydata}
add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
tox: add "coverage" environment Run with "tox -e coverage". Uses a new helper module (allmydata.test.run_trial) to let us import+execute trial without knowing exactly where the "trial" binary lives, which helps with using "coverage run" under tox.
2016-05-09 20:59:54 +00:00
[testenv:coverage]
# coverage (with --branch) takes about 65% longer to run
passenv = USERPROFILE HOMEDRIVE HOMEPATH
skip_install = True
deps = --editable=.[test]
commands =
tox: add pyflakes, which was accidentally removed from CI
2016-07-20 00:18:31 +00:00
pyflakes src static misc setup.py
tox: add "coverage" environment Run with "tox -e coverage". Uses a new helper module (allmydata.test.run_trial) to let us import+execute trial without knowing exactly where the "trial" binary lives, which helps with using "coverage run" under tox.
2016-05-09 20:59:54 +00:00
tahoe --version
coverage run --branch -m allmydata.test.run_trial --rterrors --reporter=timing {posargs:allmydata}
add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
[testenv:deprecations]
tox: use python2.7 for deprecations
2016-03-27 19:05:18 +00:00
basepython=python2.7
add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
passenv = USERPROFILE HOMEDRIVE HOMEPATH
tox.ini: skip default install We use "--deps = --editable=.[test]" to achieve three goals: * make tahoe and it's dependencies available for tests * use --editable, which is faster and allows "coverage run" to get the source filenames right * use the [test] extra, which includes "mock" Tox's default install command does the first, but doesn't use --editable, so when the "deps" stage comes around, there's already a non-editable install in place. It seems to get the [test] extra right, but it doesn't wind up with an editable install. So we disable the default install command and rely on the "deps" clause instead.
2016-05-09 20:56:06 +00:00
skip_install = True
tox.ini: use --editable to work around old-pip bug One of the buildslaves (Ubuntu wily 15.10) has a very old pip-1.5.6, which doesn't know how to "pip install" a filepath+extra (like ".[test]") unless --editable is also used. It's convenient to have --editable set anyways (so you can do subsequent narrow testing without re-running tox, by running ".tox/py27/bin/trial TESTCASE" or use .tox/py27/bin/activate), so changing the dependency from ".[test]" to "--editable=.[test]" is the easiest way to work around that older buildslave. (I could also have upgraded the buildslave to use a newer pip, but 15.10 is pretty recent and other people will probably hit this too, so this way it's fixed for everybody). refs ticket:2776
2016-04-12 21:28:02 +00:00
deps = --editable=.[test]
add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
setenv =
tox.ini: fix spelling of DeprecationWarning
2016-03-27 21:59:20 +00:00
PYTHONWARNINGS=default::DeprecationWarning
add initial tox support This adds support for two environments: 'py27' for basic tests, and 'deprecations' to run tests with deprecation warnings turned on (the latter is meant to be run from a buildbot step that knows how to count and format the warnings nicely).
2016-03-09 05:16:36 +00:00
commands =
improve run-deprecations script Rewrote in Twisted, which lets us read/scan/print all log lines in realtime. The output is now correctly interleaved (as well as maintaining the stdout-vs-stderr of each message). The renamed --warnings= logfile records all relevant lines from *both* stdout and stderr (i.e. any that includes "DeprecationWarning"), which handles a change (perhaps in recent Twisteds?) that emits these warnings on stdout instead of stderr.
2016-04-06 21:07:06 +00:00
python misc/build_helpers/run-deprecations.py --warnings=_trial_temp/deprecation-warnings.log trial --rterrors {posargs:allmydata}
move 'check-memory' from Makefile into tox.ini So use 'tox -e check-memory' instead of 'make check-memory'. The tox version will create a virtualenv and install tahoe for you before running the tests, removing one use of the 'tahoe @FILENAME' hack (which was used to run a python file with a PYTHONPATH set to import tahoe's dependencies).
2016-03-09 05:17:51 +00:00
tox: add "upcoming-deprecations" environment This runs trial against the latest (git) Twisted and Foolscap, to give us an early warning about anything we're currently doing that will become deprecated in their next releases.
2016-04-06 19:24:15 +00:00
[testenv:upcoming-deprecations]
basepython=python2.7
passenv = USERPROFILE HOMEDRIVE HOMEPATH
setenv =
PYTHONWARNINGS=default::DeprecationWarning
tox.ini: skip default install We use "--deps = --editable=.[test]" to achieve three goals: * make tahoe and it's dependencies available for tests * use --editable, which is faster and allows "coverage run" to get the source filenames right * use the [test] extra, which includes "mock" Tox's default install command does the first, but doesn't use --editable, so when the "deps" stage comes around, there's already a non-editable install in place. It seems to get the [test] extra right, but it doesn't wind up with an editable install. So we disable the default install command and rely on the "deps" clause instead.
2016-05-09 20:56:06 +00:00
skip_install = True
tox: add "upcoming-deprecations" environment This runs trial against the latest (git) Twisted and Foolscap, to give us an early warning about anything we're currently doing that will become deprecated in their next releases.
2016-04-06 19:24:15 +00:00
deps =
tox.ini: use --editable to work around old-pip bug One of the buildslaves (Ubuntu wily 15.10) has a very old pip-1.5.6, which doesn't know how to "pip install" a filepath+extra (like ".[test]") unless --editable is also used. It's convenient to have --editable set anyways (so you can do subsequent narrow testing without re-running tox, by running ".tox/py27/bin/trial TESTCASE" or use .tox/py27/bin/activate), so changing the dependency from ".[test]" to "--editable=.[test]" is the easiest way to work around that older buildslave. (I could also have upgraded the buildslave to use a newer pip, but 15.10 is pretty recent and other people will probably hit this too, so this way it's fixed for everybody). refs ticket:2776
2016-04-12 21:28:02 +00:00
--editable=.[test]
tox: add "upcoming-deprecations" environment This runs trial against the latest (git) Twisted and Foolscap, to give us an early warning about anything we're currently doing that will become deprecated in their next releases.
2016-04-06 19:24:15 +00:00
git+https://github.com/twisted/twisted
git+https://github.com/warner/foolscap
commands =
tox upcoming-deprecations: emit foolscap/twisted versions Note that Twisted doesn't do anything like Versioneer, so this will generally show e.g. "Twisted-16.1.0" for the entire interval between 16.1.0 and 16.2.0.
2016-04-06 23:34:14 +00:00
flogtool --version
improve run-deprecations script Rewrote in Twisted, which lets us read/scan/print all log lines in realtime. The output is now correctly interleaved (as well as maintaining the stdout-vs-stderr of each message). The renamed --warnings= logfile records all relevant lines from *both* stdout and stderr (i.e. any that includes "DeprecationWarning"), which handles a change (perhaps in recent Twisteds?) that emits these warnings on stdout instead of stderr.
2016-04-06 21:07:06 +00:00
python misc/build_helpers/run-deprecations.py --warnings=_trial_temp/deprecation-warnings.log trial --rterrors {posargs:allmydata}
tox: add "upcoming-deprecations" environment This runs trial against the latest (git) Twisted and Foolscap, to give us an early warning about anything we're currently doing that will become deprecated in their next releases.
2016-04-06 19:24:15 +00:00
move 'check-memory' from Makefile into tox.ini So use 'tox -e check-memory' instead of 'make check-memory'. The tox version will create a virtualenv and install tahoe for you before running the tests, removing one use of the 'tahoe @FILENAME' hack (which was used to run a python file with a PYTHONPATH set to import tahoe's dependencies).
2016-03-09 05:17:51 +00:00
[testenv:checkmemory]
commands =
rm -rf _test_memory
python src/allmydata/test/check_memory.py upload
python src/allmydata/test/check_memory.py upload-self
python src/allmydata/test/check_memory.py upload-POST
python src/allmydata/test/check_memory.py download
python src/allmydata/test/check_memory.py download-GET
python src/allmydata/test/check_memory.py download-GET-slow
python src/allmydata/test/check_memory.py receive
add 'tox -e docs', to check+render .rst files
2016-03-31 22:59:49 +00:00
# Use 'tox -e docs' to check formatting and cross-references in docs .rst
# files. The published docs are built by code run over at readthedocs.org,
# which does not use this target (but does something similar).
#
# If you have "sphinx" installed in your virtualenv, you can just do "make -C
# docs html", or "cd docs; make html".
#
# You can also open docs/_build/html/index.html to see the rendered docs in
# your web browser.
[testenv:docs]
deps = sphinx
tox.ini: skip default install We use "--deps = --editable=.[test]" to achieve three goals: * make tahoe and it's dependencies available for tests * use --editable, which is faster and allows "coverage run" to get the source filenames right * use the [test] extra, which includes "mock" Tox's default install command does the first, but doesn't use --editable, so when the "deps" stage comes around, there's already a non-editable install in place. It seems to get the [test] extra right, but it doesn't wind up with an editable install. So we disable the default install command and rely on the "deps" clause instead.
2016-05-09 20:56:06 +00:00
# normal install is not needed for docs, and slows things down
skip_install = True
add 'tox -e docs', to check+render .rst files
2016-03-31 22:59:49 +00:00
commands =
sphinx-build -b html -d {toxinidir}/docs/_build/doctrees {toxinidir}/docs {toxinidir}/docs/_build/html
Reference in New Issue Copy Permalink