-
-
Notifications
You must be signed in to change notification settings - Fork 983
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
Improve local CoreCLR support #700
Comments
@adamsitnik, what do you think, is it possible to write a test for it? I'm not sure that it should be one of our integration tests (because it takes to much time), but it would be nice to have an automatic way to test on any OS. /cc @Ky7m |
@AndreyAkinshin it's a great idea! I will implement such test and try it with our CI. If it takes too long (more than 5 minutes) I remove it. |
@adamsitnik, I think that we can introduce new project with integration tests which should be run manually. |
@AndreyAkinshin another good idea! |
…everything in temp to avoid lock conflicts with VS, #700
This is a combination of 18 commits which I squashed, the most important were: nice factory method for LocalCoreClr toolchain + removing filesToCopy (won't be needed anymore) don't use isolated nuget packages folder for non-local feeds update the tests projects to .NET Core 2.1 test nightly CoreFx builds support use --no-dependencies first, if it fails run the full mode restore and build in explicit way, let publish just publish /p:UseSharedCompilation=false by default to avoid zombie processes, run Core tests first (more likely to fail) remove old if defines that are no longer needed without .NET Core 1.1 support introduce builder for CustomCoreClrToolchain to make it easier to configure it print more diagnostic info, don't fail on first error and don't run the tests in parallel just run the self contained app without dotnet host add test for local CoreCLR and CoreFX builds, move them to a new project with can be run only manually allow to set RuntimeFrameworkVersion
It took me a LOT of time to get it working and tested for ALL OSes, but it is finally done. |
…everything in temp to avoid lock conflicts with VS, dotnet#700
…otnet#702 This is a combination of 18 commits which I squashed, the most important were: nice factory method for LocalCoreClr toolchain + removing filesToCopy (won't be needed anymore) don't use isolated nuget packages folder for non-local feeds update the tests projects to .NET Core 2.1 test nightly CoreFx builds support use --no-dependencies first, if it fails run the full mode restore and build in explicit way, let publish just publish /p:UseSharedCompilation=false by default to avoid zombie processes, run Core tests first (more likely to fail) remove old if defines that are no longer needed without .NET Core 1.1 support introduce builder for CustomCoreClrToolchain to make it easier to configure it print more diagnostic info, don't fail on first error and don't run the tests in parallel just run the self contained app without dotnet host add test for local CoreCLR and CoreFX builds, move them to a new project with can be run only manually allow to set RuntimeFrameworkVersion
…for local builds (it would most probably fail for most of the users), dotnet#700 dotnet#702
What we have today works, but is vulnerable to this problem
I want to use dotnet restore to install everything in a temp folder (not in the user/.nuget) to avoid this problem. But it takes a LOT of time so I need to implement #699 first.
Also part of the task is to verify that it works for all the OSes/
The text was updated successfully, but these errors were encountered: