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

Implement support for library tests using CG2-compiled framework and add the corresponding CI run #50127

Open
trylek opened this issue Mar 23, 2021 · 6 comments
Assignees
Milestone

Comments

@trylek
Copy link
Member

trylek commented Mar 23, 2021

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

@trylek trylek added this to the 6.0.0 milestone Mar 23, 2021
@trylek trylek self-assigned this Mar 23, 2021
@ghost
Copy link

ghost commented Mar 23, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

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

Author: trylek
Assignees: trylek
Labels:

area-Infrastructure-libraries

Milestone: 6.0.0

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Mar 23, 2021
@trylek trylek removed the untriaged New issue has not been triaged by the area owner label Mar 23, 2021
@Anipik
Copy link
Contributor

Anipik commented Aug 4, 2021

@trylek can we move this to 7.0.0 ?

@davidwrighton
Copy link
Member

Yes. We're not going to do this in the 6.0 timeframe.

@carlossanlop
Copy link
Member

@trylek @danmoseley do we still want to do this in 7.0 or should we move it to 8.0?

@trylek
Copy link
Member Author

trylek commented Jul 6, 2022

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.

@ghost
Copy link

ghost commented Jul 12, 2023

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

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

Author: trylek
Assignees: trylek
Labels:

area-Infrastructure

Milestone: Future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

5 participants