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

Add chaos resource debugging to readme #2409

Merged
merged 5 commits into from Dec 10, 2021
Merged

Conversation

benbp
Copy link
Member

@benbp benbp commented Dec 9, 2021

No description provided.

@benbp benbp requested a review from ckairen as a code owner December 9, 2021 01:28
@benbp benbp added Central-EngSys This issue is owned by the Engineering System team. Stress This issue is related to stress testing, part of our reliability pillar. labels Dec 9, 2021
@benbp benbp self-assigned this Dec 9, 2021
@check-enforcer-staging
Copy link

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:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

benbp and others added 2 commits December 9, 2021 14:01
Co-authored-by: Adam Ling (MSFT) <adam_ling@outlook.com>
@benbp benbp requested a review from yunhaoling December 9, 2021 19:21
Co-authored-by: Adam Ling (MSFT) <adam_ling@outlook.com>
@benbp
Copy link
Member Author

benbp commented Dec 10, 2021

/check-enforcer override

@benbp benbp merged commit dd03754 into Azure:main Dec 10, 2021
@benbp benbp deleted the benbp/chaos-debug branch December 10, 2021 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. Stress This issue is related to stress testing, part of our reliability pillar.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants