test-resources.json and test changes#23117
Conversation
Mohit-Chakraborty
left a comment
There was a problem hiding this comment.
Please verify the SDK behavior with the changes.
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run personalizer - net |
|
No pipelines are associated with this pull request. |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
heaths
left a comment
There was a problem hiding this comment.
Only reviewed the test resources scripts. Mainly, don't log out of the CLI you never logged into. That was only for Key Vault because the Az cmdlets don't support Managed HSMs in a deleted state yet while the azure CLI does.
Changes were made but I'm not reviewing the whole PR. Better a code owner for the rest of the source changes do that.
Mohit-Chakraborty
left a comment
There was a problem hiding this comment.
Blocking till we are ready to merge.
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - personalizer - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| { | ||
| properties.IsAutoOptimizationEnabled = false; | ||
| await adminClient.UpdatePersonalizerPropertiesAsync(properties); | ||
| await Task.Delay(30000); |
There was a problem hiding this comment.
This is not ideal. It makes the playback test take a minute.
| Assert.AreEqual(properties.ModelExportFrequency, result.ModelExportFrequency); | ||
| Assert.AreEqual(properties.RewardAggregation, result.RewardAggregation); | ||
| Assert.AreEqual(properties.RewardWaitTime, result.RewardWaitTime); | ||
| if (Environment.GetEnvironmentVariable("AZURE_TEST_MODE") == "Record") |
There was a problem hiding this comment.
There is a Mode property on the base type
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
Draftmode if it is:General Guidelines and Best Practices
Testing Guidelines
SDK Generation Guidelines
*.csprojandAssemblyInfo.csfiles have been updated with the new version of the SDK. Please double check nuget.org current release version.Additional management plane SDK specific contribution checklist:
Note: Only applies to
Microsoft.Azure.Management.[RP]orAzure.ResourceManager.[RP]Management plane SDK Troubleshooting
If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add
new servicelabel and/or contact assigned reviewer.If the check fails at the
Verify Code Generationstep, please ensure:generate.ps1/cmdto generate this PR instead of callingautorestdirectly.Please pay attention to the @microsoft.csharp version output after running
generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.Note: We have recently updated the PSH module called by
generate.ps1to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.