-
Notifications
You must be signed in to change notification settings - Fork 418
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
Omnisharp process crashing in travis #1256
Comments
beta.33 only has this change #1250 which is not packaged into OmniSharp distro. It was released from here https://travis-ci.org/OmniSharp/omnisharp-roslyn/jobs/407928780 So this shouldn't be related I think. |
Oh actually, now I see. There is also version beta.31, which was never released for linux, because the release build failed at the time. Since beta.31 was never there for non-windows, beta.33 was the first time this particular changeset was released. |
Here is what I see - when running on embedded mono
When running on global mono (I have 5.12) everything is fine. This is definitely related to #1250 as this type @DustinCampbell do you know if |
No, we don't copy |
that is a good question 😃I think it was just a sweeping upgrade of all the packages involved (@david-driscoll?) That said, you are right, we do not take advantage of any of the new extra features of this new package so I opened #1259 as a proposal to revert back to the old package and not have to modify the embedded Mono (and not have to grow its size too). The only thing is that the old package |
Cool. That's probably the right thing in the short term. In the longer term, I'll take a look at moving the scripts that I use to create the embedded Mono into the OmniSharp repo. That's a good first step towards democratizing the embedded Mono so it isn't always gated on work from me. |
We should probably add some tests that activate OmniSharp via command line args as well. |
FWIW, there are tons of warnings on build with Mac/Linux since moving to net461.
|
Yep I saw them too. I tried with Mono 5.14 preview as well, but they are still there. |
Should be fixed by mono/msbuild@393268f |
Thanks @marek-safar ! |
This has been fixed by #1260 |
The recent builds of omnisharp-vscode that consume the latest omnisharp from the master branch have been failing. On trying we realized that the versions till 1.32.2-beta.21 were working fine and the ones from
1.32.2-beta.33 onwards are failing.
Here is the link to the failing build: https://travis-ci.org/OmniSharp/omnisharp-vscode/builds/410545826
The text was updated successfully, but these errors were encountered: