-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
accidentially passing MarkInfo objects into internals creates hard to comprehend error #3515
Comments
GitMate.io thinks possibly related issues are #3170 ([pytest 3.4.0] 'NoneType' object has no attribute 'testscollected'), #3050 (deprecate pytest.config), #1882 (pytest 3.0 on Anaconda), #2984 (pytest 3.3: TerminalReporter.writer removed without deprecating it first), and #1965 (Pytest 3.0.2 memory leak with pytest.raises). |
it seems that a markinfo object was forced into the metadata at a unexpected place it doesnt happen from pytest alone, i will investigat where it is from |
the cases_64bit will set up broken marker objects |
i got a fix |
i submitted scipy/scipy#8871 to sort it out in scipy |
pytest should trigger warnings and sort out the issue internally when markinfo objects are passed |
Right, indeed the scipy code associated with that test is mucking with the pytest internals. |
@nicoddemus i beleive this one has not been sorted out |
Upgrading pytest from 3.5.1 to 3.6.0 for scipy test suite brought up some test failures. An INTERNALERROR appears in the middle of the test run, when running some tests (that use pytest.mark), apparently related to a deprecation message emitted "_pytest.deprecated.RemovedInPytest4Warning: MarkInfo objects are deprecated". The test suite is run with
filterwarnings = error
enabled, which causes the apparently internally emitted deprecation message to result to an internal error.Reproducible with
Linux/Fedora 28
The text was updated successfully, but these errors were encountered: