-
Notifications
You must be signed in to change notification settings - Fork 443
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
Update .NET Core version #246
Conversation
…on a later version than we have Fixes https://github.com/dotnet/cli/issues/10553
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay for the smoke test.
@wfurt we are trying to update to the latest version of the runtime and this is now failing for freebsd only. Could you take a look? |
It seems like something else changed as well. From the error log I see we are trying to download https://dotnetcli.azureedge.net/dotnet/Runtime/2.1.0/dotnet-runtime-2.1.0-freebsd-x64.tar.gz and that does notr exist for FreeBSD. Do you have any idea @livarcocc ? If not, I can dig into it. |
@wfurt It's supposed to be OK for that download to fail (per the comment in the code at least): https://github.com/dotnet/core-sdk/blob/master/eng/restore-toolset.sh#L16-L19 |
ok. Let me sync and do local test build on FreeBSD. |
it seems like core-setup is missing FreeBSD leg: We did not publish runtime sine 12/18 |
can you use same pool as corefx and core-setup? |
core-sdk also uses dceng There may be more to that but:
|
Cool. I wasn't aware of this new agent OS. Will give it a try. Thanks. |
I am going to disable freebsd until we have runtime bits available for it again. |
or rather, ask @dsplaisted to do it! |
Also add test to catch when ASP.NET depends on a later version than we have
Fixes https://github.com/dotnet/cli/issues/10553