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.

Sign up for GitHub

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

Jump to bottom

Generalize runtest exclusion mechanism #4747

Closed
richardlford opened this issue Dec 4, 2015 · 2 comments
Closed

Generalize runtest exclusion mechanism #4747

richardlford opened this issue Dec 4, 2015 · 2 comments
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. enhancement Product code improvement that does NOT require public API changes/additions no-recent-activity
Projects
Infrastructure Backlog
Milestone
Future

Comments

@richardlford
Copy link
Contributor

The current runtest accepts Exclude and Exclude2 options.

It would be better to collapse /Exclude and /Exclude2 into a single parameter
that is a semicolon-separated list of paths to exclude files.
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
@msftgits msftgits added this to the Future milestone Jan 30, 2020
@ghost ghost added the backlog-cleanup-candidate An inactive issue that has been marked for automated closure. label Mar 18, 2022
@ghost
Copy link

ghost commented Mar 18, 2022

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 the experimental issue cleanup initiative we are currently trialing. Please share any feedback you might have in the linked issue.

@ghost ghost added the no-recent-activity label Mar 18, 2022
@ghost
Copy link

ghost commented Apr 2, 2022

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 Apr 2, 2022
@ghost ghost locked as resolved and limited conversation to collaborators May 2, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. enhancement Product code improvement that does NOT require public API changes/additions no-recent-activity
Projects
Infrastructure Backlog
  
Future
Milestone
Future
Development

No branches or pull requests
2 participants
@richardlford @msftgits