Test improvements for Queues/ServiceBus DynamicConcurrency (#24426)#24798
Test improvements for Queues/ServiceBus DynamicConcurrency (#24426)#24798
Conversation
mathewc
requested review from
JoshLove-msft,
amishra-dev,
amnguye,
fabiocav,
jsquire,
kasobol-msft,
pakrym,
seanmcc-msft and
tg-msft
as code owners
mathewc
requested review from
kasobol-msft
and removed request for
amishra-dev,
amnguye,
fabiocav,
jsquire,
kasobol-msft,
pakrym,
seanmcc-msft and
tg-msft
|
/azp run net - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Looks like Service Bus tests are good - @kasobol-msft do you want to kick off the storage tests again or were there issues related to the dynamic concurrency tests in the previous run? |
JoshLove-msft
left a comment
JoshLove-msft
left a comment
There was a problem hiding this comment.
Looks good from SB perspective.
Yes, but we're not in position to do this right now as we're working on a regression in storage tests that destabilized pipelines.. @jaschrep-msft let's follow up here when we get pipelines in order. |
ghost
added
the
no-recent-activity
|
Hi @mathewc. Thank you, for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
ghost
closed this
|
Hi @mathewc. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass. |
Add Microsoft.StorageTasks Service | Swagger API Review (Ring 0 Service) (Azure#24798) * Add the Readme files and StorageTasks Spec file with CRUD and List by subs and rg with examples * Rectify provider namespace to Microsoft.StorageTask and refactor examples into folders * Address Lint diff failure to use the model from common-types * Update Operations API with defaut response * Add List Storage Task Assignment ARM Ids API * Add POST List Storage Task Run Report Summary API * Adding x-ms-identifiers * Spell corrections * Fix spell check errors * Add 201 response code to PUT task operation * Address minor changes and comments to reuse existing schema, update examples * Add request body to List Summary Report API, Add Example. Remove 200 status code from Delete Async * Add example reference to API file * Adding Storage task action preview API with example * Correct spelling * Addig allowed resource type constraint * Change the Reporting API to GET with Arm resource type Microsoft.StorageTasks/storageTasks/reports * Address PR comments, correct and rephrease operation ids * Change to proxy resource * Fix typo
3 participants
Addresses #24426 and #24745. Initially I was considering a larger overhaul of the tests, e.g. having a message writer that continued to write messages until concurrency increased by a certain amount. However, I think If we just adjust the message numbers and test conditions we should be able to arrive at a stable configuration.