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

Investigate VSCode-Python-Rolling-CI errors where no test reportfile output is found (catastrophic failures). #2684

Closed
d3r3kk opened this issue Sep 25, 2018 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug windows

Comments

@d3r3kk
Copy link

d3r3kk commented Sep 25, 2018

Since adding the test to ensure that test report files are output during the build, we've caught 4 instances of these test failure cases: https://vscode-python.visualstudio.com/VSCode-Python/_build/results?buildId=1273&view=logs

Windows, testSingleWorkspace, Python 3.5, 3.6, and 3.7.
Windows, testMultiWorkspace, Python 3.6

Investigate and discover if this is this a failure of the test code, or the actual code. If it is the test code, skip the failing tests and add a new backlog item to fix it. If it is the actual code, add a new backlog issue for this milestone and fix it.

@d3r3kk d3r3kk added feature-* windows bug Issue identified by VS Code Team member as probable bug labels Sep 25, 2018
@d3r3kk d3r3kk self-assigned this Sep 26, 2018
d3r3kk added a commit to d3r3kk/vscode-python that referenced this issue Sep 26, 2018
Workaround for microsoft#2684 until we get to the root cause.

- unittest.test.ts is failing with the ECONNRESET somewhere in the  method.
@d3r3kk d3r3kk closed this as completed Sep 26, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Oct 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug windows
Projects
None yet
Development

No branches or pull requests

1 participant