Fail report_failed_workflows job on hidden reporting pipeline errors#3552
Conversation
|
Hello, thanks for contributing for the first time! |
report_failed_workflows job on hidden pipeline errors
Addressed in commit 0ea4781. I removed the simulated grep-only test and updated the workflow logic itself: the step now uses |
report_failed_workflows job on hidden pipeline errorsreport_failed_workflows job on hidden reporting pipeline errors
There was a problem hiding this comment.
Pull request overview
This PR hardens the scheduled “Report Failed Workflows” GitHub Actions job so it reliably fails when the reporting pipeline encounters real command/pipeline errors, reducing the chance of silently-successful runs that didn’t actually complete the reporting logic.
Changes:
- Enabled fail-fast shell behavior in the reporting step via
set -euo pipefail. - Simplified workflow-run parsing by switching from base64-encoded JSON objects to
jq -rTSV output read directly by the shell loop.
The scheduled Report Failed Workflows job could complete successfully while still masking failures in the reporting pipeline. This update makes the step fail fast on real command/pipeline errors and simplifies parsing to reduce hidden failure modes.
Fail-fast shell semantics
report_failed_workflows.ymlrun block to useset -euo pipefailso command, unset-variable, and pipeline failures correctly fail the step/job.Safer workflow parsing path
jqdecode flow with a singlejq -rTSV output parsed directly in the shell loop.Test scope correction
tests/unit/test_unit_report_failed_workflows_uses_pipefail.sh) since it did not validate real behavior.