Mark flaky test as xfail on Python 3.5.0#5803
Conversation
|
Have you seen it without xdist? |
That's what I've tried, yes.
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. |
|
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 |
Why not just amend it here instead? :) |
blueyed
left a comment
There was a problem hiding this comment.
Should be 3.5.0, but ok with me.
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 I have changed the check to use |
|
Wait, another one failed now: test_continue_on_collection_errors |
It is a bit unfortunate that xdist provides not more information there, isn't it? |
|
Maybe the job should be changed to not use xdist? |
|
Hmmm that would probably help, let me try it. |
|
I will remove the |
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
|
🤞 |
|
Cool, for reference it might still break when using coverage with it (#5772). |
|
😓 |
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