This repository was archived by the owner on Jan 23, 2023. It is now read-only.
[ARM32/Linux] Change default CI job for ARM and clean-up#10370
Merged
Conversation
02ed24c to
824bd8a
Compare
- Change ARM CI job triggered by PR: ubuntu16.04 debug, ubuntu release, tizen debug/release - Clean-up: remove emulator build/test - Change ubuntu16.04 x64 default job name and trigger phrase: conflict triggerring with arm
824bd8a to
1586ea0
Compare
Author
|
@dotnet-bot test ci please |
Author
|
@gkhanna79 PTAL |
gkhanna79
approved these changes
Mar 22, 2017
jorive
pushed a commit
to guhuro/coreclr
that referenced
this pull request
May 4, 2017
- Change ARM CI job triggered by PR: ubuntu16.04 debug, ubuntu release, tizen debug/release - Clean-up: remove emulator build/test - Change ubuntu16.04 x64 default job name and trigger phrase: conflict triggerring with arm
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
related issue: #10185