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

[MQ reliability] The Service Bus tests occasionally fail in canary #12815

Closed
richardpark-msft opened this issue Dec 8, 2020 · 3 comments
Closed
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Service Bus
Milestone

Comments

@richardpark-msft
Copy link
Member

Now that we've reached a stable spot with our SDK we need to be particularly attentive to failures in the canary region, given that it's a first signal for potential larger customer issues.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 8, 2020
@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Service Bus labels Dec 8, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 8, 2020
@ramya-rao-a ramya-rao-a added this to the [2021] January milestone Dec 8, 2020
@jmealo
Copy link

jmealo commented Dec 10, 2020

Please add a test that runs indefinitely or at least for several days to catch the production issues that customers (we) actually faced. I would say 30-60 days would be long enough, or to just keep it running until the next release is cut.

@richardpark-msft
Copy link
Member Author

Just adding in some more context - there is conversation in this issue (#12609) that is discussing what we have and what we're putting in place for long term tests.

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this issue Feb 9, 2021
Update PIM specs for Documentation changes (Azure#12815)

* PIM API Specs

* update readme

* Update

* Update readme

* operation id fix

* name fix

* Name changes

* fix

* Fix

* Changes based on docs generated

* Scope fix in example

* Updates for documentation

* Change operation name

Co-authored-by: Aman Swaika <[email protected]>
@richardpark-msft
Copy link
Member Author

This original issue was handle some specific cases that were breaking in canary. We have broken those down into specific issues that we'll handle individually (for instance, #14441).

I am closing this particular issue in favor of tracking the more specific failures that have already been logged.

@jmealo - we've actually started doing more long-term and stress related testing across all of our messaging packages. We have really appreciated your feedback across this and other issues.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Service Bus
Projects
None yet
Development

No branches or pull requests

3 participants