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

Use different socket for Win32 test #3375



Copy link

@timemachine3030 timemachine3030 commented Oct 31, 2020

Copy link
Contributor Author

Not sure how this would specifically resolve the error in #3364 and I do not have a sauce key.

I tried testing Chrome 86, Win7, Node.js 10.0.0 multiple time with no error. Will try the Win10 failures when my VM finishes (tomorrow).

@timemachine3030 timemachine3030 marked this pull request as ready for review November 14, 2020 02:21
@timemachine3030 timemachine3030 changed the title WIP: Use different socket for Win32 test Use different socket for Win32 test Nov 14, 2020
Copy link

Now the CI works well. If it is stable enough, we can ignore.

Copy link
Contributor Author

This is still worth merging. Any developer on Windows, running the tests, will get an error.

Copy link

I think this is a good idea to have it merged, there is a large user base on Windows and this could potentially keep people from contributing in the future and we don't want that.

This was referenced Mar 18, 2021
mbargiel pushed a commit to mbargiel/axios that referenced this pull request Jan 27, 2022
* Remove the skipping of the `socket` http test

* Use different socket path for Win32

 - See:
 - Also:

* Updating axios in types to be lower case (axios#2797)

Co-authored-by: Xianming Zhong <>

Co-authored-by: Pilot <>
Co-authored-by: Remco Haszing <>
Co-authored-by: Xianming Zhong <>
Co-authored-by: Jay <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
No open projects
Awaiting triage

Successfully merging this pull request may close these issues.

None yet

4 participants