[issue1448] pytest on default does not support multi-inherited classes
New submission from James Lan <jameslan@gmail.com>: On default branch, pytest is 2.2.4.dev2, which does not support multi-inherited classes, so that test cases for both jvm and cli backend can not run. On pytest-update branch, pytest is 2.3.5dev6, fixed this issue. Please merge it back to default. BTW, will it be better to use a released version of pytest instead of dev? ---------- messages: 5559 nosy: jameslan, pypy-issue priority: critical status: unread title: pytest on default does not support multi-inherited classes ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1448> ________________________________________
Amaury Forgeot d Arc <amauryfa@gmail.com> added the comment: Do you have a precise example? Which tests are failing? ---------- nosy: +amaury status: unread -> chatting ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1448> ________________________________________
James Lan <jameslan@gmail.com> added the comment: pypy pypy/test_all.py --collectonly rpython/translator/jvm/test/test_constant.py on default, it finds 0 test cases, while on pytest-update, it finds 18 cases. ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1448> ________________________________________
mattip <matti.picus@gmail.com> added the comment: We no longer have the jvm backend. I get identical output when running python pytest.py --collectonly pypy/module as when I run the 2.5.2 version of an installed site-libraries pytest py.test --collectonly pypy/module Running collections on rpython turns up 0 tests on both versions. May I mark this invalid? If not, please provide more info. ---------- nosy: +mattip ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1448> ________________________________________
Armin Rigo <armin.rigo@gmail.com> added the comment: The problem (in my opinion) was the tests in the jvm backend using some too-new feature of py.test. Now that we dropped the tests, the problem is resolved. ---------- nosy: +arigo status: chatting -> resolved ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1448> ________________________________________
participants (4)
-
Amaury Forgeot d Arc -
Armin Rigo
-
James Lan
-
mattip