Add automatic issue creation for scheduled fuzzing job failures with area/fuzzing label filtering #823
Conversation
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
Copilot
AI
changed the title
Copilot finished work on behalf of
jsturtevant
August 26, 2025 23:12
jsturtevant
reviewed
Aug 26, 2025
Copilot
AI
changed the title
Copilot finished work on behalf of
jsturtevant
August 27, 2025 21:41
jsturtevant
reviewed
Aug 27, 2025
jsturtevant
reviewed
Aug 27, 2025
|
@copilot address feedback |
jsturtevant
reviewed
Aug 27, 2025
Copilot finished work on behalf of
jsturtevant
August 27, 2025 22:04
Copilot finished work on behalf of
jsturtevant
August 27, 2025 22:09
I've addressed the feedback by reverting to the inline approach where fuzzing steps are directly in Fuzzing.yml and the notification runs as an additional step (not a separate job) only on failure. The script includes --repo parameter support for testing as requested. |
Copilot finished work on behalf of
jsturtevant
August 27, 2025 22:24
Copilot finished work on behalf of
jsturtevant
August 27, 2025 22:32
jsturtevant
force-pushed
the
copilot/fix-181
branch
2 times, most recently
from
deed6c7 to
e29625c
Compare
jsturtevant
added
the
kind/enhancement
|
I tested running the script against my fork jsturtevant#3 closed https://github.com/jsturtevant/hyperlight-1/issues?q=is%3Aissue%20state%3Aclosed |
ludfjig
previously approved these changes
Aug 28, 2025
ludfjig
reviewed
Aug 28, 2025
Copilot
AI
changed the title
Copilot finished work on behalf of
jsturtevant
August 28, 2025 22:25
jsturtevant
force-pushed
the
copilot/fix-181
branch
from
b5856cc to
f3bac73
Compare
ludfjig
approved these changes
Aug 29, 2025
ludfjig
requested changes
Aug 29, 2025
jsturtevant
reviewed
Aug 29, 2025
Copilot
AI
changed the title
Copilot finished work on behalf of
jsturtevant
August 29, 2025 18:31
jsturtevant
reviewed
Aug 29, 2025
jsturtevant
reviewed
Aug 29, 2025
|
@copilot look at the feedback |
- Created dev/notify-fuzzing-failure.sh script to handle GitHub issue creation/updates - Modified Fuzzing.yml and dep_fuzzing.yml workflows to add failure notifications - Added proper permissions for issue creation and comments - Script checks for existing open fuzzing failure issues and either creates new ones or adds comments - Includes robust error handling and test mode for validation Co-authored-by: jsturtevant <[email protected]>
… workflow - Removed notification step and issues permission from dep_fuzzing.yml (reusable workflow) - Added separate notify-failure job to Fuzzing.yml (scheduled workflow) - This ensures issues are only created for scheduled cron job failures, not PR runs Co-authored-by: jsturtevant <[email protected]>
- Added --repo "$REPO" to gh issue comment command (line 103) - Added --repo "$REPO" to gh issue create command (line 148) - This enables testing against specific repositories by setting the REPO variable Co-authored-by: jsturtevant <[email protected]>
Signed-off-by: James Sturtevant <[email protected]>
Co-authored-by: jsturtevant <[email protected]>
Co-authored-by: jsturtevant <[email protected]>
Co-authored-by: jsturtevant <[email protected]>
jsturtevant
force-pushed
the
copilot/fix-181
branch
from
c49cab9 to
1583008
Compare
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.
fixes: #181
This PR implements automatic GitHub issue creation and management for fuzzing job failures in scheduled workflows. When fuzzing jobs fail during the weekly scheduled runs, the system automatically creates new issues or adds comments to existing ones with proper error handling and repository-standard labeling.
Key Features
area/fuzzinglabel for precise issue identification instead of title pattern matchingarea/testing,kind/bug,area/fuzzing,lifecycle/needs-review)--repoparameter for testing against different repositoriesImplementation
The notification system is implemented as an additional step in the main fuzzing job that runs only on failure (
if: failure()). All fuzzing steps from the reusable workflow have been inlined directly intoFuzzing.ymlto ensure the notification only triggers for scheduled runs, maintaining the matrix strategy for different fuzzing targets (fuzz_host_print,fuzz_guest_call,fuzz_host_call).The script searches for existing open issues with the
area/fuzzinglabel and either adds a comment to the most recent one or creates a new issue with comprehensive details including workflow run links and next steps for investigation. The label-based filtering approach eliminates pagination concerns and ensures reliable issue management by using precise label queries instead of title pattern matching.💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.