-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Makes all tests pass on Windows #1939
Conversation
special case for win32 + neovim
fixing failed test 4 of VSCodeVim#1914
|
@jpoon It has something to do with the neovim script I think. I've been busy interning (my evaluation period is coming up!) but somebody mentioned that it could have to do with our ubuntu version? I think the better thing to do is to switch to the neovim appImage. |
@jpoon if you're asking me about squashing, I'd be happy to do it, but I believe GitHub already supports this through Squash and merge |
@philipmat Could you try resolving the conflict (which should be just removing test/cmd_line/read.test.ts) and running the tests again? |
Huh. I thought github could show you what the conflicts were. |
AppVeyor is green as well: https://ci.appveyor.com/project/philipmat/vim/build/1.0.13 |
@philipmat Did you and @jpoon decide whether we want to re-integrate Appveyor checks? |
@jpoon said, and I quote:
:) Y'all would need to add a badge, though. |
I always thought that it wasn't really necessary because it's electron, but I guess that's not really true, especially with neovim as well as all other sorts of things. The main thing I'm concerned with Appveyor is tests being even more flaky, as well as increasing test times. |
The tests are not mandatory, but it's good to have signals that everything works well across all platforms VSCode runs on. If you want to ignore a broken AppVeyor build, there's nothing stoppping you. Oh, and AppVeyor seems to finish faster than Travis so there's no waiting either 😀 |
So long as Windows test fail doesn't prevent us from pushing a release, that's good 👍 All we need now is to figure out what those conflicts are... |
They're not preventing you because you're using the Travis build to push a release (AFAICT) I currently see no conflicts on this branch. Should I be looking elsewhere? |
No it's good now. Before it said that there were conflicts that needed to be resolved without showing any conflicts, so I was confused. Thanks. |
Huh. They seem to only show on web, but not on mobile. |
I just merged it on mobile... |
Fixes #1914
https://ci.appveyor.com/project/philipmat/vim/build/1.0.10