8000 refactor(ci): prune legacy trigger-demo-workload naming and job references by janzak-dev · Pull Request #919 · google/xmc · GitHub
[go: up one dir, main page]

Skip to content

refactor(ci): prune legacy trigger-demo-workload naming and job references - #919

Merged
janzak-dev merged 1 commit into
mainfrom
refactor/prune-legacy-trigger-demo-workload
Sep 18, 2026
Merged

janzak-dev merged 1 commit into
mainfrom
refactor/prune-legacy-trigger-demo-workload

Conversation

@janzak-dev
@janzak-dev janzak-dev commented Sep 18, 2026 •
Copy link
Copy Markdown
Collaborator

Summary & Context

This PR cleans up deprecated job name fallbacks (trigger-demo-workload and validate-workload-results) in .github/scripts/nightly-failure-alert.js and aligns test fixtures in .github/scripts/nightly-failure-alert.test.js with the active canonical workflow schema.

Background & Historical Context

  1. Initial Workflow Design: trigger-demo-workload.yml was originally introduced as a standalone launcher workflow in PR feat(examples): add multi-workunit simple job launch script and nightly workflow #847 and integrated into nightly-test-suite.yml in PR feat(ci): add scheduled nightly test suite workflow #852 alongside validate-workload-results.
  2. Consolidation: In PR refactor(ci): consolidate demo workload launch and verification into unified nightly workflow #895, launch and verification steps were consolidated into a single atomic job run-and-verify-demo-workload in .github/workflows/nightly-test-suite.yml. While .github/workflows/trigger-demo-workload.yml was deleted, backwards-compatibility fallbacks were retained in nightly-failure-alert.js to ensure stability across rollout branches.
  3. Canonical Nightly Workflows: As seen in the active workflow definitions:

The legacy standalone trigger-demo-workload job name is fully obsolete and has no active producers.

Key Changes

  • .github/scripts/nightly-failure-alert.js: Pruned trigger-demo-workload and validate-workload-results fallbacks in buildAlertParams. Active resolution now exclusively checks canonical jobs:
    • triggerOutcome: run-and-verify-demo-workload or run-and-verify-examples
    • verifyOutcome: run-and-verify-demo-workload or aggregate-results
  • .github/scripts/nightly-failure-alert.test.js: Updated unit test fixtures to use active job IDs (run-and-verify-demo-workload) instead of legacy names.

Verification Record

  • Unit Tests: Ran node --test .github/scripts/nightly-failure-alert.test.js (31/31 passed).
  • Full Script Suite: Ran node --test .github/scripts/*.test.js (175/175 passed across 11 suites).
  • Bazel Nightly Tests: Ran bazel test //tools/nightly_tests/... (2/2 passed).
  • Pre-Commit Checks: Passed ./.githooks/pre-commit cleanly.
  • Repository Sweep: Verified zero occurrences of trigger-demo-workload and validate-workload-results across the repo via git grep.

TAG=agy
CONV=df3c1c34-924a-42d3-81dc-9755d79b93f5

…ences

Remove deprecated trigger-demo-workload and validate-workload-results job fallbacks in nightly-failure-alert.js and align unit test fixtures with canonical workflow job IDs (run-and-verify-demo-workload, run-and-verify-examples, aggregate-results).

TAG=agy
CONV=df3c1c34-924a-42d3-81dc-9755d79b93f5
@gemini-code-assist gemini-code-assist Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the nightly failure alert script and its associated tests by removing references to the obsolete 'trigger-demo-workload' and 'validate-workload-results' workflow steps from the outcome resolution logic. There are no review comments to evaluate, and I have no feedback to provide.

@janzak-dev
janzak-dev marked this pull request as ready for review September 18, 2026 08:38
@janzak-dev
janzak-dev added this pull request to the merge queue Sep 18, 2026
Merged via the queue into main with commit 16531e9 Sep 18, 2026
12 checks passed
@janzak-dev
janzak-dev deleted the refactor/prune-legacy-trigger-demo-workload branch September 18, 2026 09:36
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

0