CoreCLR Runtime Tests aren't running on outerloop-only queues

[jkoritzinsky]

CoreCLR has some test queues defined to only run in outerloop scenarios. Specifically, there are some queues that we used to run tests only on during the official build back before repo consolidation.

This was conditioned by setting the helixQueuesGroup: property in the pipeline definitions for test jobs to all.

When we consolidated repositories, we removed the test runs on the internal pipelines, but we never moved these queues to be run on any public builds by default. This includes all CoreCLR runtime test runs on Windows 7 and Windows 8.1.

I've checked the Kusto data, and I have verified that we have not run any CoreCLR runtime tests on Windows 7 in dotnet/runtime, but we are running them on dotnet/coreclr.

cc: @AaronRobinsonMSFT

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

---

CoreCLR has some test queues defined to only run in outerloop scenarios. Specifically, there are some queues that we used to run tests only on during the official build back before repo consolidation.

This was conditioned by setting the helixQueuesGroup: property in the pipeline definitions for test jobs to all.

When we consolidated repositories, we removed the test runs on the internal pipelines, but we never moved these queues to be run on any public builds by default. This includes all CoreCLR runtime test runs on Windows 7 and Windows 8.1.

I've checked the Kusto data, and I have verified that we have not run any CoreCLR runtime tests on Windows 7 in dotnet/runtime, but we are running them on dotnet/coreclr.

cc: @AaronRobinsonMSFT

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure-coreclr
Milestone:	-

[AaronRobinsonMSFT]

/cc @ViktorHofer @BruceForstall