Skip to content

Only report bump workflow failures for scheduled runs - #7340

Closed
pietern wants to merge 1 commit into
mainfrom
pietern/f10-7312-workflow-failure-dispatch
Closed

pietern wants to merge 1 commit into
mainfrom
pietern/f10-7312-workflow-failure-dispatch

Conversation

@pietern

@pietern pietern commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Changes

The "Report failure" step in bump-go-toolchain.yml (if: failure()) and bump-vuln-deps.yml (if: failure() && !inputs.dry_run) also ran for manual workflow_dispatch runs, so a mistyped version input opened a "the scheduled workflow failed" issue and assigned seven people. Both now use if: failure() && github.event_name == 'schedule'; the report-failure action's description recommends the same gate.

Question: in bump-vuln-deps.yml this drops !inputs.dry_run, so a failed manual non-dry-run no longer reports either, and the reporter can't be tested by dispatching a run by hand. Is schedule-only what we want?

Why

Follow-up to #7312, which added the failure reporter.

Tests

  • No workflow test harness or actionlint available; checked that the three files parse as YAML and walked through each trigger (schedule failure reports, schedule success doesn't, manual runs don't).

This pull request and its description were written by Isaac.

The report-failure step ran on any failure, so a failed workflow_dispatch
run (for example a mistyped version input in bump-go-toolchain, or a
non-dry-run manual run of bump-vuln-deps) opened an issue claiming the
scheduled workflow failed and assigned seven people. Gate the step on
github.event_name == 'schedule' in both workflows; this subsumes the
!inputs.dry_run check in bump-vuln-deps.

Co-authored-by: Isaac <no-reply@databricks.com>
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: 2880490

Run: 41812276290

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 271 15 6:21
✅​ aws-windows-latest-4core-16gb 273 13 6:17
✅​ azure linux-2core-8gb 270 15 6:23
✅​ azure-windows-latest-4core-16gb 272 13 6:30
✅​ gcp linux-2core-8gb 271 15 5:48
✅​ gcp-windows-latest-4core-16gb 273 13 6:15
Top 3 slowest tests (at least 2 minutes):
duration env testname
3:32 gcp-windows-latest-4core-16gb TestAccept
3:24 azure-windows-latest-4core-16gb TestAccept
3:23 aws-windows-latest-4core-16gb TestAccept

@pietern

pietern commented Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

For manual testing of the workflow we want to create an issue on workflow_dispatch.

@pietern pietern closed this Nov 5, 2026
@pietern
pietern deleted the pietern/f10-7312-workflow-failure-dispatch branch November 5, 2026 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants