[Pytest-commit] Issue #234: Have some level of non-concurrency. (hpk42/tox)
Matthew Schinckel
issues-reply at bitbucket.org
Mon Apr 6 12:45:58 CEST 2015
New issue 234: Have some level of non-concurrency.
https://bitbucket.org/hpk42/tox/issue/234/have-some-level-of-non-concurrency
Matthew Schinckel:
I have a really nice workflow for managing coverage testing using tox: I have an envlist that looks something like:
clean,{py27,py33,py34,pypy}-django{17,18},status
The first listed environment simply removes the existing coverage data, and the final one runs the coverage status reports.
The issue is that with detox, the env `status` runs before any of the other envs have had a chance to finish.
I'd love some way of either marking that a specific env should _not_ run under detox (as it gives an error that no coverage data was found), or should run after everything else.
The only workaround I have come up with is to remove the `status` env from the envlist, and run `tox -e status` after `detox`.
More information about the pytest-commit
mailing list