[SB] tests.yml - sample live test changes#16329
Conversation
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
59240d2 to
6b07a33
Compare
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
f21085f to
aef5365
Compare
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
aef5365 to
a70ea52
Compare
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
a70ea52 to
1a82750
Compare
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| "failure_and_recovery.py", | ||
| "mgmt_queue.py", | ||
| "mgmt_rule.py", | ||
| "mgmt_subscription.py", | ||
| "mgmt_topic.py", | ||
| "proxy.py", | ||
| "receive_deferred_message_queue.py", | ||
| "receive_iterator_queue.py", | ||
| "session_pool_receive.py", | ||
| "mgmt_queue_async.py", | ||
| "mgmt_rule_async.py", | ||
| "mgmt_subscription_async.py", | ||
| "mgmt_topic_async.py", | ||
| "proxy_async.py", | ||
| "receive_deferred_message_queue_async.py", | ||
| "receive_iterator_queue_async.py", | ||
| "session_pool_receive_async.py" |
There was a problem hiding this comment.
why ignore these tests? please track all the samples being added here with issues
There was a problem hiding this comment.
created issues to track why all of these are being ignored, and that they should be removed when fixed:
- [ServiceBus] error running
receive_deferred_message_queue.pysample in live test pipeline #16649 - [ServiceBus] Creating resources with mgmt randomly results in ResourceExistsError #16645
- [EngSys] Add timeout section for long-running samples in live test pipeline #16617
- [ServiceBus] Add push mode samples to timed samples section #16642
- *[EventHubs] Add push mode samples to timed samples section #16705
| @@ -0,0 +1,220 @@ | |||
| { | |||
There was a problem hiding this comment.
dumb question: can you tell me what this file does?
There was a problem hiding this comment.
good question - It's an ARM template that's being used to create resources for samples, rather than setting the EnvVars in tests.yml. This is to align with other services, which are also moving towards using ARM templates, since they are easier to maintain than a growing list of EnvVars in the tests.yml file. Specifically, formrecognizer. Context here and issue here.
No description provided.