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

test-resources.json and test changes #23117

Merged
merged 20 commits into from
Aug 18, 2021

Conversation

orenmichaely
Copy link
Contributor

All SDK Contribution checklist:

This checklist is used to make sure that common guidelines for a pull request are followed.

  • Please open PR in Draft mode if it is:
    • Work in progress or not intended to be merged.
    • Encountering multiple pipeline failures and working on fixes.
  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • I have read the contribution guidelines.
  • The pull request does not introduce breaking changes.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
  • The *.csproj and AssemblyInfo.cs files 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] or Azure.ResourceManager.[RP]

  • Include updated management metadata.
  • Update AzureRP.props to add/remove version info to maintain up to date API versions.

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 service label and/or contact assigned reviewer.

  • If the check fails at the Verify Code Generation step, please ensure:

    • Do not modify any code in generated folders.
    • Do not selectively include/remove generated files in the PR.
    • Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
      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.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:

      `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`
    

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.

Copy link
Contributor

@Mohit-Chakraborty Mohit-Chakraborty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please verify the SDK behavior with the changes.

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run personalizer - net

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

heaths
heaths previously requested changes Aug 11, 2021
Copy link
Member

@heaths heaths left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@heaths heaths dismissed their stale review August 11, 2021 20:55

Changes were made but I'm not reviewing the whole PR. Better a code owner for the rest of the source changes do that.

@orenmichaely orenmichaely reopened this Aug 11, 2021
Copy link
Contributor

@Mohit-Chakraborty Mohit-Chakraborty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking till we are ready to merge.

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orenmichaely
Copy link
Contributor Author

/azp run net - personalizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Mohit-Chakraborty Mohit-Chakraborty merged commit a2e976c into Azure:main Aug 18, 2021
{
properties.IsAutoOptimizationEnabled = false;
await adminClient.UpdatePersonalizerPropertiesAsync(properties);
await Task.Delay(30000);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a Mode property on the base type

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants