-
Notifications
You must be signed in to change notification settings - Fork 111
Post JSON summary to report processor #1719
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
base: develop
Are you sure you want to change the base?
Conversation
|
Remember to squash merge! |
🔍Changelog Validation Results: |
🔍Version Validation Results: |
|
Remember to squash merge! |
🔍Version Validation Results: |
🔍Changelog Validation Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds automated reporting of workflow execution summaries by POSTing the machine-readable JSON summary file to a workflow analysis processor endpoint. This enables AI/LLM-based analysis to automatically identify root cause failures in WARP test workflows.
Key Changes:
- Added a new step to POST workflow summary JSON to an external API endpoint
- Configured the API call with authentication using GitHub secrets
- Updated step numbering in comments to accommodate the new step
|
Remember to squash merge! |
🔍Changelog Validation Results: |
🔍Version Validation Results: |
|
Remember to squash merge! |
🔍Changelog Validation Results: |
🔍Version Validation Results: |
40faadf to
5433677
Compare
|
Remember to squash merge! |
🔍Version Validation Results: |
🔍Changelog Validation Results: |
|
Remember to squash merge! |
🔍Changelog Validation Results: |
🔍Version Validation Results: |
|
Remember to squash merge! |
🔍Version Validation Results: |
🔍Changelog Validation Results: |
Description
Addresses
This is a follow up to #1703 . This POSTs the JSON version of the workflow summary file if it exists to the report processor.
Motivation
@kilonzi and the team have been working on using AI / LLMs to automatically generate reports that identify root cause failures of Warp test workflows. As part of this work, we need to send the JSON version of the markdown summary file that is generated at the end of a workflow run to the workflow analysis processor to generate the final report.
Checklist
If you can answer "yes" to the following items, please add a checkmark next to the appropriate checklist item(s) and notify our WARP team by tagging @broadinstitute/warp-admins in a comment on this PR.