-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Maps] Search, Route, Render test #22566
Conversation
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
5bd325a
to
57930dc
Compare
/azp run js - maps - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
17651d8
to
59b16ee
Compare
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 js - maps - c |
No pipelines are associated with this pull request. |
/azp run js - maps - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
8dbeb3b
to
d0dcf65
Compare
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - maps - tests |
No pipelines are associated with this pull request. |
/check-enforcer override |
/azp run js - maps - tests |
No pipelines are associated with this pull request. |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - maps-search - tests |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run js - maps-render - tests |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run js - maps-render - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - maps-render - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - maps-render - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - maps-route - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - maps-search - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @dubiety. 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. |
Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists