[operations] Add runbook for fuzz-mdx.yml silent-failure monitoring - #6806
[operations] Add runbook for fuzz-mdx.yml silent-failure monitoring#6806kubestellar-hive[bot] wants to merge 1 commit into
Conversation
Documents the gap tracked in #6805: fuzz-mdx.yml's weekly MDX sanitizer fuzz run only uploads a 14-day crash artifact on failure and never opens a tracking issue, unlike generate-leaderboard.yml and generate-acmm-history.yml in this repo. Adds manual detection and recovery steps until a maintainer can add the workflow-side alert (agent tokens cannot write .github/workflows/*). Signed-off-by: kubestellar-hive[bot] <223556219+Copilot@users.noreply.github.com>
|
Important Held for human sign-off on the direction, not on the code. This PR's only tracked rationale is #6805, which the hive filed itself — issue #6805 was filed by kubestellar-hive[bot] and no human has acknowledged it. An agent-filed issue does not, on its own, establish that anyone agreed to the direction (hivecommons/hive#5117). The change may well be right; nothing here is a review of it. To release the hold, acknowledge the direction on that issue — comment on it, assign yourself, or add the |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellar-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @kubestellar-hive[bot]. Thanks for your PR. I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Closing: superseded by
|
What
Adds
runbooks/fuzz-mdx-monitoring.md, documenting how to manually detect and recover from a silently-failed weekly run of.github/workflows/fuzz-mdx.yml(the MDX sanitizer fuzz harness).Why
Fixes the gap tracked in #6805:
fuzz-mdx.yml's onlyif: failure()step uploads a 14-day crash-log artifact — it never opens or updates a tracking issue, unlikegenerate-leaderboard.yml/generate-acmm-history.ymlin this repo. A crash on the unattended weekly scheduled run (as opposed to a PR check) can go unnoticed indefinitely, and the reproduction evidence (crash seed/log) is deleted after 14 days. This follows the same pattern already used forrunbooks/scorecard-monitoring.md(#6724) andrunbooks/stale-workflow-monitoring.md(#6729).The workflow-side
if: failure()alert fix itself is out of scope for this PR — it requiresworkflowspermission that agent tokens do not have, so a maintainer needs to add it directly to.github/workflows/fuzz-mdx.yml. This runbook is the bounded, non-workflow mitigation in the meantime.Scope
Docs-only change (new file under
runbooks/). No workflow, alert, or code behavior is modified.Closes: partially addresses #6805 (manual mitigation; workflow fix still needs a maintainer).
— hive: agent=operations backend=copilot model=claude-sonnet-4-6