-
Notifications
You must be signed in to change notification settings - Fork 22
[FR] Integrate xfail
#33
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
Comments
Segfaults are currently not integrated |
Is it hard to integrate them? |
i have no idea, i haven't worked on it and i don't plan to maintain/work on pytest-forked i only took it out of xdist to enable dropping the boxed feature from xdist itself |
@RonnyPfannschmidt where can I see how xfail is processed? I'm trying to figure out how things work in src/_pytest/mark/structures.py but it seems like it's probably not the place where I can hack into... I want to contribute but struggling to find a starting point. |
I vaguely recall that xfail is processed in the skipping plugin |
So it turned out that for xfail to work, I need to set |
Opened an issue about this pytest-dev/pytest#7327 |
I have a test that SEGFAULTs under random envs (usually only in one or two jobs in the matrix). So I decided to use forked to isolate it and marked it with xfail as follows:
But, despite my expectations, when it crashes, pytest shows it as a failure and not as XFAIL.
Could you please clarify whether this behavior is intended or is it a bug? (looks like a bug to me)
Am I doing anything wrong? Am I missing something here?
(Ref: https://github.com/ansible/pylibssh/runs/728770734?check_suite_focus=true#step:9:120)
The text was updated successfully, but these errors were encountered: