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

Enable outerloop helix legs on the "runtime-coreclr outerloop" pipeline. #57068

Closed

Conversation

jkoritzinsky
Copy link
Member

Also, clean up the CoreCLR helix queue configuration since we don't run any tests in the internal build.

Fixes #57007

Also, clean up the CoreCLR helix queue configuration since we don't run any tests in the internal build.

Fixes dotnet#57007
@ghost
Copy link

ghost commented Aug 9, 2021

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

Issue Details

Also, clean up the CoreCLR helix queue configuration since we don't run any tests in the internal build.

Fixes #57007

Author: jkoritzinsky
Assignees: -
Labels:

area-Infrastructure-coreclr

Milestone: -

@jkoritzinsky
Copy link
Member Author

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ViktorHofer
Copy link
Member

Also, clean up the CoreCLR helix queue configuration since we don't run any tests in the internal build.

We eventually want to run tests on internal, i.e. for MSRC servicing. We haven't yet enabled that but it is tracked in #47328 which needs to happen before we start servicing for 6.0.

I would just leave those in for now.

@jkoritzinsky
Copy link
Member Author

I'd rather we add a new Helix queues setup template when we set up the internal queues unless we're planning on using the same pipeline definition (with the same platform matrix) for servicing as we do in main.

#47328 also tracks adding running libraries tests, which will also need a helix queues file update to support running on internal queues.

@ViktorHofer
Copy link
Member

I'd rather we add a new Helix queues setup template when we set up the internal queues unless we're planning on using the same pipeline definition (with the same platform matrix) for servicing as we do in main.

That was my assumption. I don't think we would want to add another build definition entry point. Unrelated, we also have a tracking issue to merge runtime-official.yml and runtime.yml but that hasn't happened yet.

@jkoritzinsky
Copy link
Member Author

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkoritzinsky
Copy link
Member Author

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkoritzinsky
Copy link
Member Author

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkoritzinsky
Copy link
Member Author

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@danmoseley
Copy link
Member

@jkoritzinsky I'm going to close this as no progress. Feel free to reopen if you plan to revisit.

@danmoseley danmoseley closed this Feb 10, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Mar 12, 2022
@jkoritzinsky jkoritzinsky deleted the outerloop-coreclr-helix branch March 22, 2024 01:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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