Skip to content
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

Ignore Python 3.8 specific failure in pytest for now #527

Merged
merged 1 commit into from May 1, 2020

Conversation

svenstaro
Copy link
Contributor

@svenstaro svenstaro commented Apr 30, 2020

I suggest we xmark these tests for the time being until pytest upstream issues are resolved.

The failure of testdir.tmpdir on Python 2 is

/tmp/pytest-of-svenstaro/pytest-326/test_basetemp_in_subprocesses0/runpytest-0/popen-gw0/test_send0

while in Python 3 it is

/tmp/pytest-of-svenstaro/pytest-327/tmp-test_basetemp_in_subprocesses0/pytest-of-svenstaro/pytest-0/test_send0

It's not an optimal fix but at least we'll be able to more easily notice actual test failure in pytest-xdist-specific code again. Currently, everything just fails which isn't optimal.

@RonnyPfannschmidt
Copy link
Member

thanks for the markings, we will have to followup once the fixup is actually released in pytest

@svenstaro svenstaro merged commit ec13cea into master May 1, 2020
@@ -186,6 +189,7 @@ def test_crash():
)
assert result.ret == 1

@pytest.mark.xfail(reason="#527: Ignore Python 3.8 failure for the time being")
Copy link
Contributor

@blueyed blueyed Jul 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for reference: I do not think this is py38 specific, but rather pytest related only (pytest-dev/pytest#6981 (comment)).
(just leaving this here since I was confused why pytestmaster was not failing anymore)

Build log for the (now swallowed) failure: https://travis-ci.org/github/pytest-dev/pytest-xdist/jobs/669139507#L255

@nicoddemus nicoddemus deleted the ignore-python38-failure branch July 13, 2020 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants