[Pytest-commit] Issue #190: Generative setenv fails if there’s only one variable (hpk42/tox)

2014-09-25 Thread Hynek Schlawack
New issue 190: Generative setenv fails if there’s only one variable https://bitbucket.org/hpk42/tox/issue/190/generative-setenv-fails-if-there-s-only Hynek Schlawack: Consider this minimal tox.ini: ```ini [tox] envlist = py27-{a,b} [testenv] deps = b: pytest setenv = a: A = 1 commands =

[Pytest-commit] Issue #191: Generative environments are only created if the fragment is used (hpk42/tox)

2014-09-25 Thread Hynek Schlawack
New issue 191: Generative environments are only created if the fragment is used https://bitbucket.org/hpk42/tox/issue/191/generative-environments-are-only-created Hynek Schlawack: Example: ```init [tox] envlist = py27-{a,b} [testenv] deps = b: pytest commands = true ``` Makes `tox -l` compl

[Pytest-commit] commit/tox: 3 new changesets

2014-09-25 Thread commits-noreply
3 new commits in tox: https://bitbucket.org/hpk42/tox/commits/81a452f9aee1/ Changeset: 81a452f9aee1 User:hpk42 Date:2014-09-25 13:38:44+00:00 Summary: py25 not supported anymore Affected #: 1 file diff -r 73185db55d671a386d617958076d95a88f602328 -r 81a452f9aee1722b22d7b32b

[Pytest-commit] Issue #598: Ability to randomize testing order (hpk42/pytest)

2014-09-25 Thread liori
New issue 598: Ability to randomize testing order https://bitbucket.org/hpk42/pytest/issue/598/ability-to-randomize-testing-order liori: I have two types of tests: CPU-bound and IO-bound. When playing with `xdist` I realized that these tests tend to cluster, ie. there's a huge block of CPU-boun

[Pytest-commit] Issue #599: internal error at unknown location (hpk42/pytest)

2014-09-25 Thread m27315
New issue 599: internal error at unknown location https://bitbucket.org/hpk42/pytest/issue/599/internal-error-at-unknown-location m27315: I have a large pytest suite with 10,000+tests, many due to the power of parameterization! (Thanks!) Recently, I changed the backend driver to connect via p