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

Add checks for correct number of ProjectsToBuild for each TestGroup #12177

Closed
echesakov opened this issue Mar 4, 2019 · 3 comments
Closed

Add checks for correct number of ProjectsToBuild for each TestGroup #12177

echesakov opened this issue Mar 4, 2019 · 3 comments
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity
Milestone

Comments

@echesakov
Copy link
Contributor

As suggested by @BruceForstall it would be nice to have checks similar to what added in dotnet/coreclr#19290 but for each TestGroup from dotnet/coreclr#22885

@echesakov echesakov changed the title Add checks to build-test.cmd/build-test.sh for each TestGroup Add checks for correct number of ProjectsToBuild for each TestGroup Mar 4, 2019
@echesakov
Copy link
Contributor Author

/cc @dotnet/jit-contrib

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@ghost
Copy link

ghost commented Sep 4, 2023

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@ghost ghost added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Sep 4, 2023
@ghost
Copy link

ghost commented Sep 18, 2023

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@ghost ghost closed this as completed Sep 18, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Oct 18, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity
Projects
Archived in project
Development

No branches or pull requests

2 participants