Configured CosmosDB Local Emulator for running integration tests on the Windows agent#1876
Merged
Aniruddh25 merged 1 commit intomainfrom Nov 9, 2023
Merged
Conversation
Aniruddh25
approved these changes
Nov 9, 2023
Collaborator
Aniruddh25
left a comment
There was a problem hiding this comment.
LGTM! Thanks for this mitigation.
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
seantleonard
approved these changes
Nov 9, 2023
Contributor
seantleonard
left a comment
There was a problem hiding this comment.
Thanks for adding this change! looking forward to follow up on adjusting macos/linux runners.
Aniruddh25
pushed a commit
that referenced
this pull request
Nov 13, 2023
…he Windows agent (#1876) ## Why make this change? Currently, we are running integration tests against a production CosmosDB account. Recently, we've encountered 429 errors during these tests because the same production account is used for each OS agent. To address this issue, we have started using the CosmosDB Local Emulator when running integration tests on the Windows agent. ## What is this change? Changed the Windows agent to windows-latest. This agent has an emulator preinstalled. Removed the FileTransform task for the Windows agent. Temporarily removed the Mac-os job to prevent 429 errors. Todo: Use an emulator in the Mac-os agent and Linux agent. ## How was this tested? - [x] Integration Tests Co-authored-by: Neeraj Sharma (from Dev Box) <[email protected]>
Aniruddh25
added a commit
that referenced
this pull request
Nov 13, 2023
## Why make this change? This is simply cherry-picking the following PRs before creating the next stable 0.9 version: - #1876 - #1821 - #1854 - #1851 - #1872 - #1868 --------- Co-authored-by: Sean Leonard <[email protected]> Co-authored-by: Abhishek Kumar <[email protected]> Co-authored-by: neeraj-sharma2592 <[email protected]> Co-authored-by: Neeraj Sharma (from Dev Box) <[email protected]> Co-authored-by: aaronburtle <[email protected]>
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 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.
Why make this change?
Currently, we are running integration tests against a production CosmosDB account. Recently, we've encountered 429 errors during these tests because the same production account is used for each OS agent. To address this issue, we have started using the CosmosDB Local Emulator when running integration tests on the Windows agent.
What is this change?
Changed the Windows agent to windows-latest. This agent has an emulator preinstalled.
Removed the FileTransform task for the Windows agent. Temporarily removed the Mac-os job to prevent 429 errors.
Todo: Use an emulator in the Mac-os agent and Linux agent.
How was this tested?