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

Skip existing tests that have consistently been failing in Rolling-CI #2795

Closed
d3r3kk opened this issue Oct 4, 2018 · 1 comment
Closed
Assignees
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc.

Comments

@d3r3kk
Copy link

d3r3kk commented Oct 4, 2018

Many tests are still failing in our rolling CI builds that have been failing for longer than our ADO pipeline has been running them.

To facilitate maintaining current quality levels we must skip these known-to-fail tests until we get time to adequately fix them.

For each known-failing test, add code that will skip for the OS(s), for the python version(s) it is known to fail in only.

Once the Rolling-CI test runs green, ensure all new failures cause the build to fail completely.

@d3r3kk d3r3kk added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Oct 4, 2018
@d3r3kk d3r3kk self-assigned this Oct 17, 2018
@d3r3kk
Copy link
Author

d3r3kk commented Oct 18, 2018

Tests disabled to achieve this:

#2544 Returning correct blank lines/unicode chars Win-py2.7
#2545 Autopep 526 Win/macOS-py3.4-py3.5
#2546 ProcessService & unicode under Win-py2.7
#2547 Import from .env file Win-py2.7
#2548 (newer, but still unfixed) Unittests run multiple Win/macOS-py3.4

@lock lock bot locked as resolved and limited conversation to collaborators Nov 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Projects
None yet
Development

No branches or pull requests

2 participants