-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flaky tests in Python 3.5.0 with xdist 馃槵 #5795
Labels
type: infrastructure
improvement to development/releases/CI structure
Comments
nicoddemus
added
the
type: infrastructure
improvement to development/releases/CI structure
label
Aug 28, 2019
4 tasks
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Aug 30, 2019
Related to pytest-dev#5795
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Aug 30, 2019
nicoddemus
changed the title
test_exit_on_collection_with_maxfail_bigger_than_n_errors flaky in py35 馃槵
test_exit_on_collection_with_maxfail_bigger_than_n_errors flaky in Python 3.5.0 馃槵
Aug 30, 2019
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Aug 30, 2019
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
changed the title
test_exit_on_collection_with_maxfail_bigger_than_n_errors flaky in Python 3.5.0 馃槵
Flaky tests in Python 3.5.0 with xdist 馃槵
Aug 30, 2019
Unfortunately py35, without xdist and coverage, still is crashing randomly. Unless someone has other ideas, I think we should consider not testing Does flake8 now cover most gotchas related to poor typing in 3.5.0? |
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Sep 6, 2019
This causes flaky test failures (crashes). Closes pytest-dev#5795.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Jan 10, 2020
Python 3.5.0 caused flaky failures before (pytest-dev#5795), hopefully this is more stable. This is pulled out of pytest-dev#6435, which adds code specific for Python < 3.5.2, and therefore it makes sense to test it.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Jan 11, 2020
Python 3.5.0 caused flaky failures before (pytest-dev#5795), hopefully this is more stable. This is pulled out of pytest-dev#6435, which adds code specific for Python < 3.5.2, and therefore it makes sense to test it.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Jan 12, 2020
Python 3.5.0 caused flaky failures before (pytest-dev#5795). This is pulled out of pytest-dev#6435, which adds code specific for Python < 3.5.2. It only runs a specific test, while collecting everything to get coverage of the version specific code around typing.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Jan 12, 2020
Python 3.5.0 caused flaky failures before (pytest-dev#5795). This is pulled out of pytest-dev#6435, which adds code specific for Python < 3.5.2. It only runs a specific test, while collecting everything to get coverage of the version specific code around typing.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Jan 14, 2020
Python 3.5.0 caused flaky failures before (pytest-dev#5795). This is pulled out of pytest-dev#6435, which adds code specific for Python < 3.5.2. It only runs a specific test, while collecting everything to get coverage of the version specific code around typing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://travis-ci.org/pytest-dev/pytest/jobs/577770604
馃槵
In #5803 (comment), we suspect this is related to 3.5.0, as we have never seen this failure before started testing on that Python version on Travis.
The text was updated successfully, but these errors were encountered: