Skip to content

/ pytest

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

Jump to bottom

Enable xfail_strict in pytest's own suite #2722

Closed
nicoddemus opened this issue Aug 26, 2017 · 1 comment
Closed

Enable xfail_strict in pytest's own suite #2722

nicoddemus opened this issue Aug 26, 2017 · 1 comment
Labels
type: infrastructure

Comments

@nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented Aug 26, 2017

Same reasoning as in tox-dev/tox#587
@RonnyPfannschmidt
Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt commented Aug 29, 2017

there is some irony in the fact that breaking xfail because some people wanted flaky tests menas we now have to use the workaround around that broken leg ourselfes
nicoddemus added a commit to nicoddemus/pytest that referenced this issue Sep 5, 2017
@nicoddemus
Set xfail_strict=True in pytest's own test suite
Loading status checks…
10d43bd 
Fix pytest-dev#2722
@nicoddemus nicoddemus mentioned this issue Sep 5, 2017
Merged
thisch added a commit to thisch/pytest that referenced this issue Sep 22, 2017
@nicoddemus @thisch
Set xfail_strict=True in pytest's own test suite
03799d4 
Fix pytest-dev#2722
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: infrastructure
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@RonnyPfannschmidt @nicoddemus