Skip to content

Fix skipping test_UNC_path on AppVeyor due to a different error being raised #1920

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

Merged
merged 1 commit into from
Jun 2, 2017

Conversation

segevfiner
Copy link
Contributor

We get ERROR_BAD_NETPATH (53) on AppVeyor which is translated to ENOENT (2).

Let AppVeyor run this of course first.

… raised

We get `ERROR_BAD_NETPATH` (53) on AppVeyor which is translated to
ENOENT (2).
@zware
Copy link
Member

zware commented Jun 2, 2017

AppVeyor is investigating why this changed; see appveyor/ci#1579.

@zooba
Copy link
Member

zooba commented Jun 2, 2017

Sure, but ENOENT is an equally good reason to skip network share tests. It's clearly an environmental issue and not ours (or am I missing something?)

zware pushed a commit to zware/cpython that referenced this pull request Jun 4, 2017
… being raised (pythonGH-1920)

We get `ERROR_BAD_NETPATH` (53) on AppVeyor which is translated to
ENOENT (2).
(cherry picked from commit 7a99625)
zware pushed a commit to zware/cpython that referenced this pull request Jun 4, 2017
… being raised (pythonGH-1920)

We get `ERROR_BAD_NETPATH` (53) on AppVeyor which is translated to
ENOENT (2).
(cherry picked from commit 7a99625)
zware added a commit that referenced this pull request Jun 4, 2017
… being raised (GH-1920)

We get `ERROR_BAD_NETPATH` (53) on AppVeyor which is translated to
ENOENT (2).
(cherry picked from commit 7a99625)
zware added a commit that referenced this pull request Jun 4, 2017
… being raised (GH-1920)

We get `ERROR_BAD_NETPATH` (53) on AppVeyor which is translated to
ENOENT (2).
(cherry picked from commit 7a99625)
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.

4 participants