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

Running CoreCLR tests on Mono : Investigate and hook up running the with PRs/CI, making sure any change in CoreCLR or Mono triggers these test run on Mono #33255

Closed
SamMonoRT opened this issue Mar 5, 2020 · 4 comments
Assignees
Labels
area-Infrastructure-mono runtime-mono specific to the Mono runtime

Comments

@SamMonoRT
Copy link
Member

Referring to comments in PR : #33176
Investigate and hook up running the CoreCLR tests during PRs/CI, making sure any change in CoreCLR or Mono triggers these test run on Mono

@SamMonoRT SamMonoRT added area-Infrastructure runtime-mono specific to the Mono runtime labels Mar 5, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Mar 5, 2020
@naricc
Copy link
Contributor

naricc commented Mar 9, 2020

@akoeplinger

@akoeplinger
Copy link
Member

akoeplinger commented Mar 10, 2020

@directhex can you please take a look at this one when you have time? It should only need copying the .yml from CoreCLR runs (CoreCLR Pri0 Test Build and CoreCLR Pri0 Test Run) and passing in one additional property.

@naricc
Copy link
Contributor

naricc commented Mar 25, 2020

My draft PR is here: #34054

@SamMonoRT SamMonoRT removed the untriaged New issue has not been triaged by the area owner label Jun 22, 2020
@SamMonoRT
Copy link
Member Author

We can close this one. We are tracking this via the table in #33381

@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-mono runtime-mono specific to the Mono runtime
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants