-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Implement support for library tests using CG2-compiled framework and add the corresponding CI run #50127
Comments
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsAs part of the switch-over from Crossgen1 to Crossgen2 we should start running regular library test runs over CG2-compiled framework to catch potential regressions or issues. We should update the library test build scripts to optionally support CG2 compilation of framework assemblies, add the corresponding support to the YAML scripts and define a new type of run leveraging this functionality to run library tests over CG2-compiled framework. For now I would run them on a daily basis; if they turn out to be stable enough, we may consider switching some of the library tests in PR runs to work this this too. /cc @dotnet/runtime-infrastructure, @dotnet/crossgen-contrib
|
@trylek can we move this to 7.0.0 ? |
Yes. We're not going to do this in the 6.0 timeframe. |
@trylek @danmoseley do we still want to do this in 7.0 or should we move it to 8.0? |
I don't think this is strictly necessary in 7.0. It's kind of nice to have but, as it's an infrastructure change, it doesn't need to be tightly coupled with a particular release. In fact I believe this to be the perfect candidate for a quality week project. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsAs part of the switch-over from Crossgen1 to Crossgen2 we should start running regular library test runs over CG2-compiled framework to catch potential regressions or issues. We should update the library test build scripts to optionally support CG2 compilation of framework assemblies, add the corresponding support to the YAML scripts and define a new type of run leveraging this functionality to run library tests over CG2-compiled framework. For now I would run them on a daily basis; if they turn out to be stable enough, we may consider switching some of the library tests in PR runs to work this this too. /cc @dotnet/runtime-infrastructure, @dotnet/crossgen-contrib
|
As part of the switch-over from Crossgen1 to Crossgen2 we should start running regular library test runs over CG2-compiled framework to catch potential regressions or issues. We should update the library test build scripts to optionally support CG2 compilation of framework assemblies, add the corresponding support to the YAML scripts and define a new type of run leveraging this functionality to run library tests over CG2-compiled framework. For now I would run them on a daily basis; if they turn out to be stable enough, we may consider switching some of the library tests in PR runs to work this this too.
/cc @dotnet/runtime-infrastructure, @dotnet/crossgen-contrib
The text was updated successfully, but these errors were encountered: