-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 CLI version to support Ubuntu on Windows #18259
Comments
Just to be clear, I'm referring to the CLI that gets installed into the Tools directory. |
Yes, I think it is. |
Is there an ETA for getting this updated? |
Getting buildtools on RTM shared framework is tracked by dotnet/buildtools#954. It's been preempted repeatedly but I got a RTM buildtools running (doing a build on Windows) yesterday afternoon. I'm aiming for a PR this morning although there might be delays in making sure it's compatible across repos/platforms. |
dotnet/corefx#11387 seems to have enabled builds in Bash on Windows. |
The latest Windows 10 preview builds contain enough functionality in Ubuntu/Bash on Windows (a.k.a. Windows Subsystem for Linux, or WSL) that .NET Core mostly works now. With the fix for #11058, we can even build/test the CoreFx tree in this environment. Currently there are a few test failures; I've been working on identifying the causes of these, and filing bugs in the appropriate repos. This change implements workarounds for all of the current known issues in the "inner loop" tests. Mostly, I've just conditionally disabled tests when running in the WSL environment. There is still an issue, under investigation, causing non-deterministic failures in the System.Net.Http tests (microsoft/WSL#1068). And I haven't tried OuterLoop runs of anything but the networking tests.
Windows preview build 14905 now has enough kernel support to build/test CoreFx in the Ubuntu on Windows environment. However, the CLI build we are using still has the "execstack" issue, and so will not run on Ubuntu on Windows. This was fixed in the CoreCLR repo in April, and current public CLI builds seem to have the fix.
Can we update the CLI version in CoreFx to include the fix for https://github.com/dotnet/coreclr/issues/4048?
The text was updated successfully, but these errors were encountered: