-
Notifications
You must be signed in to change notification settings - Fork 5k
Remove duplicate android and wasm yaml templates to run the runtime tests after a "global-build" build step. #80157
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
Remove duplicate android and wasm yaml templates to run the runtime tests after a "global-build" build step. #80157
Conversation
…ests after a "global-build" build step.
/azp list |
Tagging subscribers to this area: @directhex Issue DetailsI'm planning on utilizing this template in #74623 with CoreCLR and I noticed that we had two very similar copies. I figured it was a good idea to collapse them into a single copy and make it work for CoreCLR for at least simple cases.
|
/azp run runtime-android, runtime-androidemulator |
Azure Pipelines successfully started running 1 pipeline(s), but failed to run 1 pipeline(s). |
/azp run runtime-android, runtime-androidemulator |
Azure Pipelines successfully started running 2 pipeline(s). |
I merged the wasm template into build-runtime-tests-and-send-to-helix.yml but I guess I didn't think to also merge in the android one. Thanks for cleaning that up. |
/azp run runtime-android |
Azure Pipelines successfully started running 1 pipeline(s). |
Failure is #79874. Merging this in to unblock my other work. |
I'm planning on utilizing this template in #74623 with CoreCLR and I noticed that we had two very similar copies. I figured it was a good idea to collapse them into a single copy and make it work for CoreCLR for at least simple cases.