-
-
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
3.2.0: exceptions / internal errors related to markers #2573
Comments
Thanks!
Looking at the message, it is also not helpful at all; most users don't know what a @RonnyPfannschmidt could you take a look at this? |
I can reproduce this with a simple xfailing test: import pytest
@pytest.mark.xfail()
def test_foo():
assert False and launching pytest with |
Thanks! This also makes it clear to me that we should always test deprecations, and that they should be tested regarding the message in normal operation and when using |
I assumed initially that Executing your sample with
So I think the warning is being issued incorrectly as there's nothing wrong with that usage. @RonnyPfannschmidt what do you think? |
As far as I know, I refactored all usages of parametrized marks to use |
Good guy Florian. 😁 |
@nicoddemus this relates to not extracting marks form markinfo, unfortunately im not able to follow up in a timely manner atm |
FWIW if we can't easily solve this I'd vote for removing the deprecation, releasing v3.2.0, and then re-introducing it once this is fixed. |
👍 |
As discussed in pytest-dev#2573, this change introduced a serious regression. Fix pytest-dev#2573 This reverts commit 0d0b01b.
Opened a PR reverting that change. |
@The-Compiler can this one be closed? |
Do we have a reminder to re-introduce the warning? |
this will be part of providing a alternative and i expect to finish it for 3.4 o 3.4 |
I just tried the 3.2.0 pre-release with qutebrowser. First I get this during some tests:
and then it fails entirely:
The text was updated successfully, but these errors were encountered: