[SchemaRegistry] migrate to test proxy #23438
Conversation
ghost
added
the
|
/azp run python - schemaregistry - ci |
|
Pull request contains merge conflicts. |
|
/azp run python - schemaregistry - ci |
|
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: |
yunhaoling
left a comment
yunhaoling
left a comment
There was a problem hiding this comment.
LGTM! thanks for doing this migration!
|
/azp run python - schemaregistry - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hello @swathipil! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
|
/azp run python - schemaregistry - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - schemaregistry - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ghost
merged commit 
fixes Azure#22517 - need to ignore pylint `import-error` due to same issue as here: pylint-dev/pylint#2862
fixes Azure#22517 - need to ignore pylint `import-error` due to same issue as here: pylint-dev/pylint#2862
…into new_metrics_advisor * 'main' of https://github.com/Azure/azure-sdk-for-python: (62 commits) pass polling interval 0 for playback (Azure#23514) [webpubsub] switch to customizations code (Azure#23504) [AutoRelease] t2-netapp-2022-02-11-58164(Do not merge) (Azure#23214) [Key Vault] Address architect feedback (Azure#23475) Sync eng/common directory with azure-sdk-tools for PR 2910 (Azure#23499) check content (Azure#23496) fix cspell issues (Azure#22948) API Key Not Being Passed On Paged Requests (Azure#23477) [AutoRelease] t2-labservices-2022-03-14-64385 (Azure#23492) [Release issue status] fix date bug and serve Python only (Azure#23491) [SchemaRegistry] migrate to test proxy (Azure#23438) [compute] update test (Azure#23456) update servicebus test (Azure#23401) Update search test (Azure#23341) Update resources test (Azure#23340) Update relay test (Azure#23339) Update notificationhubs test (Azure#23338) Update network-dns test (Azure#23337) update network test (Azure#23421) update logic (Azure#23463) ...
2 participants
fixes #22517
import-errordue to same issue as here: Running pylint on namespace modules results in import-error pylint-dev/pylint#2862