From builds at drone.io  Wed Aug  5 00:50:23 2015
From: builds at drone.io (Drone.io Build)
Date: Tue, 04 Aug 2015 22:50:23 +0000
Subject: [Pytest-commit] [FAIL] pytest-xdist - # 12
Message-ID: <20150804224013.5521.81977@drone.io>

Build Failed

Build      : https://drone.io/bitbucket.org/pytest-dev/pytest-xdist/12
Project    : https://drone.io/bitbucket.org/pytest-dev/pytest-xdist

Repository : https://bitbucket.org/pytest-dev/pytest-xdist
Version    : 205:7d14297f39c8
Author     : Floris Bruynooghe <flub at devork.be>
Branch     : tests-for-session-testscollected

Message:
close branch

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-commit/attachments/20150804/f2aafb59/attachment.html>

From builds at drone.io  Wed Aug  5 22:06:35 2015
From: builds at drone.io (Drone.io Build)
Date: Wed, 05 Aug 2015 20:06:35 +0000
Subject: [Pytest-commit] [FAIL] pytest-xdist - # 13
Message-ID: <20150805200625.53985.64527@drone.io>

Build Failed

Build      : https://drone.io/bitbucket.org/pytest-dev/pytest-xdist/13
Project    : https://drone.io/bitbucket.org/pytest-dev/pytest-xdist

Repository : https://bitbucket.org/pytest-dev/pytest-xdist
Version    : 196:57da4bf2c1e7
Author     : Ronny Pfannschmidt <opensource at ronnypfannschmidt.de>
Branch     : remove-nondist

Message:
simplify HostRsync constructor

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-commit/attachments/20150805/602a6425/attachment.html>

From issues-reply at bitbucket.org  Thu Aug  6 19:10:05 2015
From: issues-reply at bitbucket.org (vr2262)
Date: Thu, 06 Aug 2015 17:10:05 -0000
Subject: [Pytest-commit] Issue #268: Can't use Selenium with Tox (hpk42/tox)
Message-ID: <20150806171005.14912.75422@app03.ash-private.bitbucket.org>

New issue 268: Can't use Selenium with Tox
https://bitbucket.org/hpk42/tox/issues/268/cant-use-selenium-with-tox

vr2262:

Steps to reproduce:

1. Install `selenium` in a new virtual environment.
2. Create the file `test_selenium.py` with the contents:

        #!python

        import unittest

        from selenium import webdriver


        class TestBroken(unittest.TestCase):
            def setUp(self):
                self.driver = webdriver.Firefox()

            def tearDown(self):
                self.driver.quit()

            def test_broken(self):
                pass


3. Execute `$ python -m unittest`:

        .
        ----------------------------------------------------------------------
        Ran 1 test in 1.103s

        OK

4. Install `tox`.
5. Create the file `tox.ini` with the contents:

        [tox]
        skipsdist=True

        [testenv]
        deps=selenium
        commands=python -m unittest

6. Execute `$ tox`:

        python installed: selenium==2.47.1,wheel==0.24.0
        python runtests: PYTHONHASHSEED='275551244'
        python runtests: commands[0] | python -m unittest
        E/usr/lib64/python3.4/unittest/case.py:605: ResourceWarning: unclosed file <_io.BufferedWriter name='/dev/null'>
          outcome.errors.clear()

        ======================================================================
        ERROR: test_selenium (test_selenium.TestSelenium)
        ----------------------------------------------------------------------
        Traceback (most recent call last):
          File "/.../test_selenium.py", line 8, in setUp
            self.driver = webdriver.Firefox()
          File "/.../.tox/python/lib/python3.4/site-packages/selenium/webdriver/firefox/webdriver.py", line 77, in __init__
            self.binary, timeout),
          File "/.../.tox/python/lib/python3.4/site-packages/selenium/webdriver/firefox/extension_connection.py", line 49, in __init__
            self.binary.launch_browser(self.profile)
          File "/.../.tox/python/lib/python3.4/site-packages/selenium/webdriver/firefox/firefox_binary.py", line 68, in launch_browser
            self._wait_until_connectable()
          File "/.../.tox/python/lib/python3.4/site-packages/selenium/webdriver/firefox/firefox_binary.py", line 98, in _wait_until_connectable
            raise WebDriverException("The browser appears to have exited "
        selenium.common.exceptions.WebDriverException: Message: The browser appears to have exited before we could connect. If you specified a log_file in the FirefoxBinary constructor, check it for details.


        ----------------------------------------------------------------------
        Ran 1 test in 1.060s

        FAILED (errors=1)
        ERROR: InvocationError: '/.../.tox/python/bin/python -m unittest'
        _________________________________________________________________ summary __________________________________________________________________
        ERROR:   python: commands failed




From issues-reply at bitbucket.org  Mon Aug 10 12:16:48 2015
From: issues-reply at bitbucket.org (torfuspolymorphus)
Date: Mon, 10 Aug 2015 10:16:48 -0000
Subject: [Pytest-commit] Issue #269: Python 2.5 environment uses Python 2.7
 interpreter (hpk42/tox)
Message-ID: <20150810101648.12771.43906@app12.ash-private.bitbucket.org>

New issue 269: Python 2.5 environment uses Python 2.7 interpreter
https://bitbucket.org/hpk42/tox/issues/269/python-25-environment-uses-python-27

torfuspolymorphus:

When I use tox to create a Python 2.5 environment it somehow picks up a Python 2.7 interpreter instead. All other Python versions work fine, as does Python 2.5 on its own:


```
#!bash

$ cat tox.ini 
[tox]
envlist = py25,py26,py27,py33,py34
skipsdist = True

[testenv]
commands = python --version

$ tox
py25 installed: wheel==0.24.0
py25 runtests: PYTHONHASHSEED='285314601'
py25 runtests: commands[0] | python --version
Python 2.7.6
py26 installed: argparse==1.3.0,wheel==0.24.0
py26 runtests: PYTHONHASHSEED='285314601'
py26 runtests: commands[0] | python --version
Python 2.6.9
py27 installed: wheel==0.24.0
py27 runtests: PYTHONHASHSEED='285314601'
py27 runtests: commands[0] | python --version
Python 2.7.6
py33 create: /home/torf/tmp/toxtest/.tox/py33
py33 installed: wheel==0.24.0
py33 runtests: PYTHONHASHSEED='285314601'
py33 runtests: commands[0] | python --version
Python 3.3.6
py34 create: /home/torf/tmp/toxtest/.tox/py34
py34 installed: wheel==0.24.0
py34 runtests: PYTHONHASHSEED='285314601'
py34 runtests: commands[0] | python --version
Python 3.4.0
______________ summary ______________
  py25: commands succeeded
  py26: commands succeeded
  py27: commands succeeded
  py33: commands succeeded
  py34: commands succeeded
  congratulations :)

$ python2.5 --version
Python 2.5.6

$ .tox/py25/bin/python --version
Python 2.7.6

$ tox --version
2.1.1 imported from /usr/local/lib/python2.7/dist-packages/tox/__init__.pyc
```

This is on Ubuntu 14.04.




From issues-reply at bitbucket.org  Mon Aug 17 12:58:48 2015
From: issues-reply at bitbucket.org (Karthik Borkar)
Date: Mon, 17 Aug 2015 10:58:48 -0000
Subject: [Pytest-commit] Issue #770: Exception while using getfixture call
 in doctests for pytest > 2.4.2 with module scoped fixture
 (pytest-dev/pytest)
Message-ID: <20150817105848.22698.92133@app09.ash-private.bitbucket.org>

New issue 770: Exception while using getfixture call in doctests for pytest > 2.4.2 with module scoped fixture
https://bitbucket.org/pytest-dev/pytest/issues/770/exception-while-using-getfixture-call-in

Karthik Borkar:

In** pytest > 2.4.2**

my conftest.py file


```
#!python

@pytest.fixture(scope="module")
def config(request):
    ....
```

my doc file

```
#!doc

.. testsetup:: [*]

    >>> from lib.ShellExecutor import *
    >>> shell=ShellExecutor(getfixture('config'))
...
```

When i run the doc test, i get this error

```
#!error

001 .. testsetup:: [*]
002 
003     >>> from lib.ShellExecutor import *
004     >>> shell = ShellExecutor(getfixture('config'))
UNEXPECTED EXCEPTION: AssertionError(u'assert None',)
Traceback (most recent call last):

  File "/usr/lib64/python2.6/doctest.py", line 1253, in __run
    compileflags, 1) in test.globs

  File "<doctest view-command-history.rst[1]>", line 1, in <module>

  File "/home/dev/Qubole/docs/doc_new/lib/python2.6/site-packages/pytest-2.7.0-py2.6.egg/_pytest/python.py", line 1383, in getfuncargvalue
    return self._get_active_fixturedef(argname).cached_result[0]

  File "/home/dev/Qubole/docs/doc_new/lib/python2.6/site-packages/pytest-2.7.0-py2.6.egg/_pytest/python.py", line 1399, in _get_active_fixturedef
    result = self._getfuncargvalue(fixturedef)

  File "/home/dev/Qubole/docs/doc_new/lib/python2.6/site-packages/pytest-2.7.0-py2.6.egg/_pytest/python.py", line 1458, in _getfuncargvalue
    subrequest.node)

  File "/home/dev/Qubole/docs/doc_new/lib/python2.6/site-packages/pytest-2.7.0-py2.6.egg/_pytest/python.py", line 1233, in node
    return self._getscopeitem(self.scope)

  File "/home/dev/Qubole/docs/doc_new/lib/python2.6/site-packages/pytest-2.7.0-py2.6.egg/_pytest/python.py", line 1480, in _getscopeitem
    assert node

AssertionError: assert None

```
This works fine with **pytest == 2.4.2** as i was using this for sometime now. Error only in **pytest >= 2.4.2**

and also in **pytest > 2.4.2**  i used function scoped fixture, it worked


```
#!python

@pytest.fixture(scope="function")
def config(request):
```

There is no error, doctest working fine





From issues-reply at bitbucket.org  Wed Aug 19 02:11:12 2015
From: issues-reply at bitbucket.org (Kent Wills)
Date: Wed, 19 Aug 2015 00:11:12 -0000
Subject: [Pytest-commit] Issue #771: -n0 broken (pytest-dev/pytest)
Message-ID: <20150819001112.32767.11580@app02.ash-private.bitbucket.org>

New issue 771: -n0 broken
https://bitbucket.org/pytest-dev/pytest/issues/771/n0-broken

Kent Wills:

Previously a `-n 0` option would turn off xdist and use the normal pytest behavior.

This is useful to us because we've configured our testing to be parallel by default, but sometimes single-threaded debugging is necessary.



From issues-reply at bitbucket.org  Mon Aug 24 23:55:18 2015
From: issues-reply at bitbucket.org (Alexandre Conrad)
Date: Mon, 24 Aug 2015 21:55:18 -0000
Subject: [Pytest-commit] Issue #270: skipdist and usedevelop don't play well
 together (hpk42/tox)
Message-ID: <20150824215518.30241.53725@app14.ash-private.bitbucket.org>

New issue 270: skipdist and usedevelop don't play well together
https://bitbucket.org/hpk42/tox/issues/270/skipdist-and-usedevelop-dont-play-well

Alexandre Conrad:

I'm trying to do usedevelop and skipsdist at the same time but it feels that they are multially exclusive with tox.

I have 2 tasks, `py34` and `pep8`. When I run py34 I want to use `usedevelop=true` but when I run `pep8` I don't want my project to be installed at all and use `skipsdist=true`.

Please correct me if I'm wrong: skipsdist is only a global setting recognized under the section `[tox]` which would then skip the sdist step for all `[testenv]` sections which in turns would ignore any `usedevelop=true` flag since it's tox will not even try to install the testenv in the first place.

Can we have `skipsdist` be recognized under a `[testenv]`?

```
#!ini

[tox]
envlist = py34, pep8

[testenv]
usedevelop = true
deps =
    -rtest-requirements.txt
commands =
    py.test {posargs:tests/}

[testenv:pep8]
skipsdist = true
basepython = python3.4
deps = flake8
commands =
    flake8 pricingsvc/ --max-line-length=100

[pytest]
addopts =
    --junitxml=junit.xml
    --cov=pricingsvc --cov-report=xml --cov-report=term-missing
    --verbose
```



From issues-reply at bitbucket.org  Fri Aug 28 00:01:53 2015
From: issues-reply at bitbucket.org (=?utf-8?b?SmFuIFZsxI1pbnNrw70=?=)
Date: Thu, 27 Aug 2015 22:01:53 -0000
Subject: [Pytest-commit] Issue #271: Let `tox --listenvs` list all defined
 environments, not only from `envlist` in `[tox]` section (hpk42/tox)
Message-ID: <20150827220153.2530.67473@app03.ash-private.bitbucket.org>

New issue 271: Let `tox --listenvs` list all defined environments, not only from `envlist` in `[tox]` section
https://bitbucket.org/hpk42/tox/issues/271/let-tox-listenvs-list-all-defined

Jan Vl?insk?:

Issue #52 asks for having a command to list all configured environments.

However, I found, that it lists only those environments, which are in `envlist`.

If I do not want to run some of the environments when `tox` is invoked without any argument, I keep the `envlist` in `[tox]` shorter. However, this does not print it out when::

```
$ tox -l
```

It would be nice to list all existing environments.

tox version: 2.1.1

OS: Debian Jessie

Python 2.7.9

Sample `tox.ini`:


```
#!ini

# 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 = help
skipsdist = true

[testenv:help]
basepython = python2.7
commands = python -c "print(open('tox.help').read());" 
deps =

[testenv:docs]
basepython = python2.7
whitelist_externals =
    make
changedir = docs
commands = make html
deps = 
    -rrequirements-docs.txt

[testenv:testsamples]
basepython = python2.7
envdir = {toxworkdir}/test
commands = py.test -sv tests/test_samples.py
deps =
    -rrequirements-json.txt

[testenv:testschema]
basepython = python2.7
envdir = {toxworkdir}/test
commands = py.test -sv tests/test_schema.py
deps =
    -rrequirements-json.txt

[testenv:testyaml]
basepython = python2.7
envdir = {toxworkdir}/test
commands = py.test -sv tests/test_sample.py --yamlsample []
deps =
    -rrequirements-json.txt

[testenv:testjson]
basepython = python2.7
envdir = {toxworkdir}/test
commands = py.test -sv tests/test_sample.py --jsonsample []
deps =
    -rrequirements-json.txt

```

For given `tox.ini` it lists only `help`:

```
#!bash

$ tox --listenvs
help
```
and I would like to see there all:

```
#!bash

$ tox --listenvs
help
docs
testsamples
testschema
testyaml
testjson
```




From issues-reply at bitbucket.org  Mon Aug 31 18:07:51 2015
From: issues-reply at bitbucket.org (itxaka serrano)
Date: Mon, 31 Aug 2015 16:07:51 -0000
Subject: [Pytest-commit] Issue #272: Allo pre-test and post-test hooks so
 plugins con implement actual stuff (hpk42/tox)
Message-ID: <20150831160751.9723.11022@app11.ash-private.bitbucket.org>

New issue 272: Allo pre-test and post-test hooks so plugins con implement actual stuff
https://bitbucket.org/hpk42/tox/issues/272/allo-pre-test-and-post-test-hooks-so

itxaka serrano:

Rigth now the plugin system is kind of limited as it does not really allow to do that much.

Allowing some pre and post hooks will allow to create plugins that do actual stuff and can expand tox a lot.

real world scenario:
we run tests for an openstack dashboard on top of horizon dashboard.
we need to run a couple of docker containers to support the proper testing of our app
we want to run them locally and on jenkins
they need to be shut down automatically at the end of the tests

with tox there is no way of doing this and also DRY by sharing steps between testenvs.

By having a pre and post it would be able to create a tox-docker plugin that reads the tox config, set ups the proper containers, exposes the containers data trougth the setenvs and cleans them when the test start.

that is just an example, you coul also do the same with emails on failure, storing application logs for checking them afterwards and so on.