Repository navigation
study: run the AIOpsLab audit against a proposed fix that records the deployed workloads - #27
Merged
Merged
Conversation
… deployed workloads
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
workload_check.patch, a proposed fix for AIOpsLab's mitigation verifiers, and lets the audit run against it.eval()then fails if one of themno longer exists or is scaled to zero.
to be off.
--runs, so the patched runs go toruns-patched/with their own ledger. It stops when anepisode saves no result.
The patch makes the same changes as the upstream proposal, microsoft/AIOpsLab#209. The results come in a separate PR.