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

Roslyn 2.6.0 + C# 7.2 #1055

Merged
merged 8 commits into from
Dec 21, 2017
Merged

Roslyn 2.6.0 + C# 7.2 #1055

merged 8 commits into from
Dec 21, 2017

Conversation

filipw
Copy link
Member

@filipw filipw commented Dec 11, 2017

  • upgraded to Roslyn 2.6.0
  • added C# 7.2 support
  • added a C# 7.2 test for scripting (scripting by design should default to latest language version)
  • fixed some tests that contained invalid C#

Copy link
Contributor

@DustinCampbell DustinCampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I think you found all of the places. 😄

@filipw
Copy link
Member Author

filipw commented Dec 11, 2017

@DustinCampbell thanks! there is however a weird issue on Travis which seems legit. any idea what could cause this weird exception on Mono?

�[39;49m�[31m    OmniSharp.Roslyn.CSharp.Tests.RenameFacts.Rename_DoesTheRightThingWhenDocumentIsNotFound [FAIL]
�[39;49m�[37m      System.AggregateException : One or more errors occurred.
�[39;49m�[37m      ---- System.ArgumentException : checksum must be a SHA-1 hash

The only related thing I found is this dotnet/roslyn#22794, could it be a regression on Mono of some sort?

@DustinCampbell
Copy link
Contributor

I think you're right. The exception is coming from here: https://github.com/dotnet/roslyn/blob/de8b37a43d13aeea3a7a8b6bdf33e8363ada4da2/src/Workspaces/Core/Portable/Workspace/Solution/Checksum.cs#L30.

I've pinged that PR to see it can be ported to Roslyn master. I don't think this is a regression in Mono. It looks more like some subtle change in Roslyn's solution checksum caused it. I'm starting a mail thread internally to raise the priority.

@filipw filipw added the blocked label Dec 11, 2017
@filipw
Copy link
Member Author

filipw commented Dec 11, 2017

Adding a blocked label - pending dotnet/roslyn#23722

@DustinCampbell
Copy link
Contributor

DustinCampbell commented Dec 14, 2017

@filipw : The 2.6.1 Roslyn packages are now available on nuget.org.

@filipw
Copy link
Member Author

filipw commented Dec 15, 2017

perfect! I updated this PR and now the checks are all passing 🎉

@filipw filipw removed the blocked label Dec 15, 2017
Copy link
Member

@david-driscoll david-driscoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@filipw
Copy link
Member Author

filipw commented Dec 21, 2017

@david-driscoll @DustinCampbell I'm punching this in then 😇

@filipw filipw merged commit f224846 into OmniSharp:master Dec 21, 2017
@filipw filipw deleted the feature/roslyn-2.6.0 branch December 21, 2017 14:25
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.

3 participants