Add hosted cobalt crank profiles and runs #2105
Open
+1,397
−0
Conversation
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
… the conventions in the azure linux 3 update PR, and added the benchmarks_ci_cobalt.json file to include the cobalt machines and to match the tests of the Azure Linux VMs ci.
LoopedBard3
force-pushed
the
AddHostedCrankRuns
branch
from
5d07b2c to
f4e2976
Compare
…s updated the cobalt machines to only use 1 queue for now.
LoopedBard3
force-pushed
the
AddHostedCrankRuns
branch
from
f4e2976 to
416b39b
Compare
|
Does hosted mean these are the machines that are VMs that we have created on our physical hardware? |
Yes. |
…e AL3 machines. Generated the pipeline yaml file for the cobalt hosted machines.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add hosted cobalt crank profiles and runs. This includes adding the cobalt hosted machine setups to the ci.setup.yml, aspnet.profile.yml, and aspnet.standard.profile.yml files, adding the hosted cobalt ci configuration file, and adding the hosted cobalt ci run itself.
If we think including these with the already running benchmarks_ci runs makes more sense, we can do that. I will just be interested in ideas on what we think a good practice will be for ensuring the local vnet machine tests don't try to use the cobalt machines.
This also brings back testing for the ARM (80 and 26 core) scenarios removed here:
#2099
A new pipeline will need to be created to run these.