Skip to content

Mark flaky test as xfail on Python 3.5.0 - #5803

Merged
nicoddemus merged 1 commit into
pytest-dev:masterfrom
nicoddemus:flaky-5795
Aug 30, 2019
Merged

Mark flaky test as xfail on Python 3.5.0#5803
nicoddemus merged 1 commit into
pytest-dev:masterfrom
nicoddemus:flaky-5795

Conversation

@nicoddemus

Copy link
Copy Markdown
Member

I've tried to reproduce the issue, but it seems to only happen sporadically on Linux.

Mark it is flaky now to avoid people wasting time on PRs when they encounter this problem.

Related to #5795

@nicoddemus nicoddemus changed the title Mark flaky test as xfail Mark flaky test as xfail on py35 Aug 30, 2019
@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor

Have you seen it without xdist?
It is also related to 3.5.0 likely, not 3.5.x?

@nicoddemus

Copy link
Copy Markdown
Member Author

Have you seen it without xdist?

That's what I've tried, yes.

It is also related to 3.5.0 likely, not 3.5.x?

Good point, have not tried that.

Either way, I think it is fine to merge this; if/when someone champions this, we just remove that line of code. It is worst to have this failing randomly on PRs and generating friction, IMHO.

@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor

Sure. I just got the impression that it started to happen after explicitly testing 3.5.0.

@nicoddemus

Copy link
Copy Markdown
Member Author

Sure. I just got the impression that it started to happen after explicitly testing 3.5.0.

You got a point, I will mention it in the issue. If you are OK with the PR, could you approve please? Thanks

@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor

You got a point, I will mention it in the issue.

Why not just amend it here instead? :)

@blueyed blueyed left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should be 3.5.0, but ok with me.

@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor

Have you seen it without xdist?

That's what I've tried, yes.

So you've not seen it yourself? "it seems to only happen sporadically on Linux." refers to the CI job then?

@nicoddemus

nicoddemus commented Aug 30, 2019

Copy link
Copy Markdown
Member Author

So you've not seen it yourself? "it seems to only happen sporadically on Linux." refers to the CI job then?

Yep, and on Linux only, which we use 3.5.0 (on Windows we use 3.5.4 I think). So you are probably right that is 3.5.0 related.

I have changed the check to use 3.5.0 then, thanks!

@nicoddemus nicoddemus changed the title Mark flaky test as xfail on py35 Mark flaky test as xfail on Python 3.5.0 Aug 30, 2019
@nicoddemus

Copy link
Copy Markdown
Member Author

Wait, another one failed now: test_continue_on_collection_errors

@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor
__________________________ testing/test_collection.py __________________________
[gw1] linux -- Python 3.5.0 /home/travis/build/pytest-dev/pytest/.tox/py35-xdist/bin/python
worker 'gw1' crashed while running 'testing/test_collection.py::test_continue_on_collection_errors'

It is a bit unfortunate that xdist provides not more information there, isn't it?

@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor

Maybe the job should be changed to not use xdist?

@nicoddemus

Copy link
Copy Markdown
Member Author

Hmmm that would probably help, let me try it.

@nicoddemus

Copy link
Copy Markdown
Member Author

I will remove the xfail marker, let's see how it fares without xdist for awhile then.

Due to the flaky tests in 3.5.0, drop running
py35 with xdist for now in the hope we get better error
messages.

Ref: pytest-dev#5795
@nicoddemus

Copy link
Copy Markdown
Member Author

🤞

@nicoddemus
nicoddemus merged commit 667c646 into pytest-dev:master Aug 30, 2019
@nicoddemus
nicoddemus deleted the flaky-5795 branch August 30, 2019 15:30
@blueyed

blueyed commented Aug 30, 2019

Copy link
Copy Markdown
Contributor

Cool, for reference it might still break when using coverage with it (#5772).

@nicoddemus

Copy link
Copy Markdown
Member Author

😓

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.

2 participants