@@ -14,9 +14,11 @@ set -o pipefail
1414# # This script assumes that the gh cli is installed and in the PATH
1515# # and that there is a GitHub PAT in the GITHUB_TOKEN env var
1616# # with the following permissions:
17- # # - repo (read/write)
1817# # - issues (read/write)
1918# # or that the user is logged into the gh cli with an account with those permissions
19+ # #
20+ # # Run this script locally like:
21+ # # GITHUB_REPOSITORY="fork/hyperlight" GITHUB_RUN_ID=1 ./dev/notify-fuzzing-failure.sh "fuzz_host_print,fuzz_guest_call,fuzz_host_call"
2022
2123REPO=" ${GITHUB_REPOSITORY:- hyperlight-dev/ hyperlight} "
2224WORKFLOW_RUN_URL=" ${GITHUB_SERVER_URL:- https:// github.com} /${REPO} /actions/runs/${GITHUB_RUN_ID:- unknown} "
@@ -91,13 +93,7 @@ if [ "$FUZZING_ISSUE_COUNT" -gt 0 ]; then
9193**Workflow Run:** [$WORKFLOW_RUN_URL ]($WORKFLOW_RUN_URL )
9294**Fuzzing Targets:** $FUZZING_TARGETS
9395
94- The scheduled fuzzing job has failed again. Please check the workflow logs and artifacts for details.
95-
96- ### Next Steps
97- - [ ] Review the workflow logs for error details
98- - [ ] Download and analyze any crash artifacts
99- - [ ] Determine if this is a new issue or related to existing problems
100- - [ ] Fix the underlying issue causing the fuzzing failures"
96+ The scheduled fuzzing job has failed again. Please check the workflow logs and artifacts for details."
10197
10298 # Add comment to the existing issue
10399 if gh issue comment " $ISSUE_NUMBER " --body " $COMMENT_BODY " --repo " $REPO " ; then
@@ -129,7 +125,6 @@ The fuzzing workflow failed during execution. Please check the workflow logs and
129125- [ ] Download and analyze any crash artifacts if available
130126- [ ] Determine the root cause of the failure
131127- [ ] Fix the underlying issue
132- - [ ] Verify the fix by running fuzzing locally or waiting for the next scheduled run
133128
134129### Related Documentation
135130- [Fuzzing README](https://github.com/$REPO /blob/main/fuzz/README.md)
0 commit comments