Mailman 3 October 2012 - pytest-dev

[py-dev] [hpk42/pytest] Sporadic exceptions on xdist run (issue #216)
by Anonymous Oct. 31, 2012

Oct. 31, 2012

--- you can reply above this line --- New issue 216: Sporadic exceptions on xdist run https://bitbucket.org/hpk42/pytest/issue/216/sporadic-exceptions-on-xdist-r… Anonymous: When running with the xdist plugin and on multiple processors, I get every 2-3 runs an exception. My system is a Debian Linux testing with the following versions: This is py.test version 2.2.4, imported from /usr/lib/python2.7/dist-packages/pytest.pyc setuptools registered plugins: pytest-xdist-1.8 at /usr/lib/python2.7/dist-packages/xdist/plugin.pyc ``` #!python INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 74, in wrap_session INTERNALERROR> doit(config, session) INTERNALERROR> File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 106, in _main INTERNALERROR> config.hook.pytest_runtestloop(session=session) INTERNALERROR> File "/usr/lib/python2.7/dist-packages/_pytest/core.py", line 421, in __call__ INTERNALERROR> return self._docall(methods, kwargs) INTERNALERROR> File "/usr/lib/python2.7/dist-packages/_pytest/core.py", line 432, in _docall INTERNALERROR> res = mc.execute() INTERNALERROR> File "/usr/lib/python2.7/dist-packages/_pytest/core.py", line 350, in execute INTERNALERROR> res = method(**kwargs) INTERNALERROR> File "", line 47, in pytest_runtestloop INTERNALERROR> File "/usr/lib/python2.7/dist-packages/execnet/gateway_base.py", line 413, in receive INTERNALERROR> raise self._getremoteerror() or EOFError() INTERNALERROR> EOFError ``` I don't really know what the cause is or what's the best method to debug this. So feel free to ask me for more info. My email is calvin AT sourceforge.net. -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] split up testing/test_python.py (issue #215)
by Ronny Pfannschmidt Oct. 31, 2012

Oct. 31, 2012

--- you can reply above this line --- New issue 215: split up testing/test_python.py https://bitbucket.org/hpk42/pytest/issue/215/split-up-testing-test_pythonpy Ronny Pfannschmidt: 3 kloc isnt managable anymore, its goten hard to figure the right place for a test i think we should split the file up -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] pytest blows up when collecting modules with uninspectable objects (issue #214)
by Thomas Waldmann Oct. 31, 2012

Oct. 31, 2012

--- you can reply above this line --- New issue 214: pytest blows up when collecting modules with uninspectable objects https://bitbucket.org/hpk42/pytest/issue/214/pytest-blows-up-when-collectin… Thomas Waldmann: werkzeug/flask offers some threadlocals to comfortable access stuff like (http) request, session, (wsgi) app, etc. - those objects are special and only valid when a request is running or an app was created. if you access them before / after they are valid, it'll raise a RuntimeError. while collecting tests, pytest (since 2.3) accesses all module-level objects and tries to inspect them for a specific attribute, causing a RuntimeError exception when it does that on such special objects. thus, the usual code used in about every flask app makes pytest unusable: from flask import request, session # <- threadlocals a simple patch that solves the issue is attached. -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] Issue with numpy arrays and pytest.mark.parametrize (issue #213)
by astrofrog Oct. 28, 2012

Oct. 28, 2012

--- you can reply above this line --- New issue 213: Issue with numpy arrays and pytest.mark.parametrize https://bitbucket.org/hpk42/pytest/issue/213/issue-with-numpy-arrays-and astrofrog: The following tests used to pass: ``` import pytest import numpy as np @pytest.mark.parametrize(('error'), [1., 'spam', np.ones((5, 5))]) def test(error): pass ``` but in the latest tip (5de7185c2891) I get the following exception: ``` _________________________________________________ ERROR collecting astropy/nddata/tests/test_nddata.py _________________________________________________ /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/runner.py:121: in __init__ > self.result = func() /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/main.py:366: in _memocollect > return self._memoizedcall('_collected', lambda: list(self.collect())) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/main.py:287: in _memoizedcall > res = function() /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/main.py:366: in <lambda> > return self._memoizedcall('_collected', lambda: list(self.collect())) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:348: in collect > return super(Module, self).collect() /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:281: in collect > res = self.makeitem(name, obj) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:293: in makeitem > collector=self, name=name, obj=obj) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/main.py:157: in call_matching_hooks > return hookmethod.pcall(plugins, **kwargs) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/core.py:426: in pcall > return self._docall(methods, kwargs) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/core.py:433: in _docall > res = mc.execute() /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/core.py:351: in execute > res = method(**kwargs) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:185: in pytest_pycollect_makeitem > return list(collector._genfunctions(name, obj)) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:309: in _genfunctions > gentesthook.pcall(plugins, metafunc=metafunc) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/core.py:426: in pcall > return self._docall(methods, kwargs) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/core.py:433: in _docall > res = mc.execute() /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/core.py:351: in execute > res = method(**kwargs) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:105: in pytest_generate_tests > metafunc.parametrize(*marker.args, **marker.kwargs) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:687: in parametrize > scopenum) /Users/tom/Library/Python/2.7/lib/python/site-packages/pytest-2.3.2-py2.7.egg/_pytest/python.py:601: in setmulti > if val == _notexists: E ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all() ``` -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] Small documentation improvement. (issue #212)
by Anonymous Oct. 28, 2012

Oct. 28, 2012

--- you can reply above this line --- New issue 212: Small documentation improvement. https://bitbucket.org/hpk42/pytest/issue/212/small-documentation-improvement Anonymous: IMHO the documentation in Fixtures as Function arguments (funcargs) could be improved. As first time reader of that section I found that: ““ Here, the test_function needs the smtp fixture value ““ could be minimal :-) better understandable if it where: ““ Here, the test_ehlo function needs the smtp fixture value ““ Thanks ! -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] @pytest.setup as shortcut for @pytest.fixture(autouse=True)?
by holger krekel Oct. 28, 2012

Oct. 28, 2012

Hi, I find myself providing examples with "autouse" fixtures and am now wondering if to introduce a @pytest.setup(...) decorator as a shortcut for @pytest.fixture(..., autouse=True). Many people are used to the concept of "setup" functions getting automatically called so i think naming-wise it should fit nicely. It's slightly redundant but then again a nice shortcut?! best, holger

3 3

[py-dev] [hpk42/pytest] using --looponfail with tests that forks leaves processes lieing around (issue #211)
by Alex Gaynor Oct. 28, 2012

Oct. 28, 2012

--- you can reply above this line --- New issue 211: using --looponfail with tests that forks leaves processes lieing around https://bitbucket.org/hpk42/pytest/issue/211/using-looponfail-with-tests-th… Alex Gaynor: If you have a test uses `os.fork()` and run it with `--looponfail` from pytest-xdist then you will get a bunch of processes leaked. These processes just sit around waiting for a lock (as far as I can tell), and hog a bunch of RAM. I'm not sure what the right fix is, but right not it means every once in a while I have to kill all the processes to free up memory! (This is currently observed with pytest 2.2.4.dev2 from pypy, and pytest-xdist 1.8, I'll try with newer versions once PyPy either upgrades are removes the hardcoded pytest). -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] mistake in the documentation version (issue #210)
by evgi Oct. 27, 2012

Oct. 27, 2012

--- you can reply above this line --- New issue 210: mistake in the documentation version https://bitbucket.org/hpk42/pytest/issue/210/mistake-in-the-documentation-v… evgi: The version in sphinx conf.py is 2.4.2 and not 2.3.2 -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] ValueError: compile(): unrecognised flags (issue #209)
by James Laska Oct. 26, 2012

Oct. 26, 2012

--- you can reply above this line --- New issue 209: ValueError: compile(): unrecognised flags https://bitbucket.org/hpk42/pytest/issue/209/valueerror-compile-unrecognise… James Laska: With the 2.3.2 release, it seems pytest is now failing on my python-2.4.3 environment. Sadly, I'm unable to upgrade python in this environment. My environment consists of ... * python-2.4.3 * py-1.4.11 * pytest-2.3.2 ``` #!pre # python setup.py test running test running egg_info creating cloud_app_sanity.egg-info writing cloud_app_sanity.egg-info/PKG-INFO writing top-level names to cloud_app_sanity.egg-info/top_level.txt writing dependency_links to cloud_app_sanity.egg-info/dependency_links.txt writing manifest file 'cloud_app_sanity.egg-info/SOURCES.txt' reading manifest file 'cloud_app_sanity.egg-info/SOURCES.txt' writing manifest file 'cloud_app_sanity.egg-info/SOURCES.txt' running build_ext Checking .pth file support in . /usr/bin/python -E -c pass Searching for pytest Reading http://cheeseshop.python.org/pypi/pytest/ Reading http://pytest.org Reading http://cheeseshop.python.org/pypi/pytest/2.3.2 Best match: pytest 2.3.2 Downloading http://pypi.python.org/packages/source/p/pytest/pytest-2.3.2.zip Processing pytest-2.3.2.zip Running pytest-2.3.2/setup.py -q bdist_egg --dist-dir /tmp/easy_install-qcpd1a/pytest-2.3.2/egg-dist-tmp--9oYJ_ File "build/bdist.linux-x86_64/egg/_pytest/assertion/rewrite.py", line 37 PYC_EXT = ".py" + ("c" if __debug__ else "o") ^ SyntaxError: invalid syntax File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/assertion/rewrite.py", line 37 PYC_EXT = ".py" + ("c" if __debug__ else "o") ^ SyntaxError: invalid syntax Installed /var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg Searching for py>=1.4.11 Reading http://cheeseshop.python.org/pypi/py/ Reading http://cheeseshop.python.org/pypi/py/1.3.4 Reading http://pylib.org Reading http://cheeseshop.python.org/pypi/py/1.3.3 Reading http://cheeseshop.python.org/pypi/py/1.3.2 Reading http://cheeseshop.python.org/pypi/py/1.3.1 Reading http://cheeseshop.python.org/pypi/py/1.3.0 Reading http://cheeseshop.python.org/pypi/py/1.4.4 Reading http://cheeseshop.python.org/pypi/py/1.4.5 Reading http://cheeseshop.python.org/pypi/py/1.4.6 Reading http://cheeseshop.python.org/pypi/py/1.4.7 Reading http://cheeseshop.python.org/pypi/py/1.4.0 Reading http://cheeseshop.python.org/pypi/py/1.4.1 Reading http://cheeseshop.python.org/pypi/py/1.4.2 Reading http://cheeseshop.python.org/pypi/py/1.4.3 Reading http://cheeseshop.python.org/pypi/py/1.4.8 Reading http://cheeseshop.python.org/pypi/py/1.4.9 Reading http://cheeseshop.python.org/pypi/py/0.9.2 Reading http://codespeak.net/py/0.9.2/download.html Reading http://cheeseshop.python.org/pypi/py/1.0.2 Reading http://cheeseshop.python.org/pypi/py/1.1.1 Reading http://cheeseshop.python.org/pypi/py/1.1.0 Reading http://cheeseshop.python.org/pypi/py/1.2.0 Reading http://cheeseshop.python.org/pypi/py/1.2.1 Reading http://cheeseshop.python.org/pypi/py/1.4.10 Reading http://cheeseshop.python.org/pypi/py/1.4.11 Best match: py 1.4.11 Downloading http://pypi.python.org/packages/source/p/py/py-1.4.11.zip Processing py-1.4.11.zip Running py-1.4.11/setup.py -q bdist_egg --dist-dir /tmp/easy_install-f1Qfss/py-1.4.11/egg-dist-tmp-zbTJjS Installed /var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/py-1.4.11-py2.4.egg Running: pytest -v -l --tb=native --junitxml=results/1351254011.xml --resultlog=results/1351254011.log -k audreyvm -unregister testsuite INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/main.py", line 77, in wrap_session INTERNALERROR> config.pluginmanager.do_configure(config) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/core.py", line 268, in do_configure INTERNALERROR> config.hook.pytest_configure(config=self._config) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/core.py", line 422, in __call__ INTERNALERROR> return self._docall(methods, kwargs) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/core.py", line 433, in _docall INTERNALERROR> res = mc.execute() INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/core.py", line 351, in execute INTERNALERROR> res = method(**kwargs) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/assertion/__init__.py", line 54, in pytest_configure INTERNALERROR> warn_about_missing_assertion(mode) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/pytest-2.3.2-py2.4.egg/_pytest/assertion/reinterpret.py", line 22, in __init__ INTERNALERROR> source = source.getstatement(f.lineno, assertion=True) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/py-1.4.11-py2.4.egg/py/_code/source.py", line 105, in getstatement INTERNALERROR> start, end = self.getstatementrange(lineno, assertion) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/py-1.4.11-py2.4.egg/py/_code/source.py", line 114, in getstatementrange INTERNALERROR> ast, start, end = getstatementrange_ast(lineno, self) INTERNALERROR> File "/var/audrey/tooling/user/KATELLO_REGISTER/cloud-app-sanity/py-1.4.11-py2.4.egg/py/_code/source.py", line 364, in getstatementrange_ast INTERNALERROR> astnode = compile(content, "source", "exec", 1024) # 1024 for AST INTERNALERROR> ValueError: compile(): unrecognised flags ``` -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] pytest-2.3.2: bug fixes, unittest/trial compat, speed
by holger krekel Oct. 25, 2012

Oct. 25, 2012

pytest-2.3.2: some fixes and more traceback-printing speed =========================================================================== pytest-2.3.2 is another stabilization release with a few improvements: - issue 205: fixes a regression with conftest detection - issue 208/29: fixes traceback-printing speed in some bad cases - fix teardown-ordering for parametrized setups - fix unittest and trial compat behaviour with respect to runTest() methods - issue 206 and others: some improvements to packaging - fix issue127 and others: improve some docs See http://pytest.org/ for general information. To install or upgrade pytest: pip install -U pytest # or easy_install -U pytest best, holger krekel Changes between 2.3.1 and 2.3.2 ----------------------------------- - fix issue208 and fix issue29 use new py version to avoid long pauses when printing tracebacks in long modules - fix issue205 - conftests in subdirs customizing pytest_pycollect_makemodule and pytest_pycollect_makeitem now work properly - fix teardown-ordering for parametrized setups - fix issue127 - better documentation for pytest_addoption and related objects. - fix unittest behaviour: TestCase.runtest only called if there are test methods defined - improve trial support: don't collect its empty unittest.TestCase.runTest() method - "python setup.py test" now works with pytest itself - fix/improve internal/packaging related bits: - exception message check of test_nose.py now passes on python33 as well - issue206 - fix test_assertrewrite.py to work when a global PYTHONDONTWRITEBYTECODE=1 is present - add tox.ini to pytest distribution so that ignore-dirs and others config bits are properly distributed for maintainers who run pytest-own tests

1 0