-
-
Notifications
You must be signed in to change notification settings - Fork 11k
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
Use different socket for Win32 test #3375
Conversation
Co-authored-by: Xianming Zhong <chinesedfan@qq.com>
…3030/axios into cleanup/remove-test-skipping
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). |
Now the CI works well. If it is stable enough, we can ignore. |
This is still worth merging. Any developer on Windows, running the tests, will get an error. |
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. |
* Remove the skipping of the `socket` http test * Use different socket path for Win32 - See: https://github.com/nodejs/node-v0.x-archive/blob/master/test/simple/test-pipe-stream.js#L73 - Also: https://github.com/nodejs/node-v0.x-archive/blob/master/test/common.js#L39 * Updating axios in types to be lower case (axios#2797) Co-authored-by: Xianming Zhong <chinesedfan@qq.com> Co-authored-by: Pilot <timemachine@ctrl-c.club> Co-authored-by: Remco Haszing <remcohaszing@gmail.com> Co-authored-by: Xianming Zhong <chinesedfan@qq.com> Co-authored-by: Jay <jasonsaayman@gmail.com>
Use different socket path for Win32