ci: [DO NOT MERGE] demo — validate observe-aborted-jobs runner-shutdown detection#57268
ci: [DO NOT MERGE] demo — validate observe-aborted-jobs runner-shutdown detection#57268cmur2 wants to merge 1 commit into
Conversation
🔍 CI Failure AnalysisGHA workflow run: #214081 Found 34 unsuccessful job(s) 📋 GHA job:
|
GitHub moved the runner-shutdown message ("The runner has received a
shutdown signal.") out of job annotations into the raw job logs, so
observe-aborted-jobs stopped recording these events. This manually
dispatched workflow reproduces the condition: it runs a long sleep on a
self-hosted (preemptible) runner that can be stopped/preempted mid-job,
then runs observe-aborted-jobs to confirm the abort is detected and
recorded again.
Not for merge — demo/verification only.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
9957b0c to
dcaf784
Compare
Why
GitHub changed how runner preemptions are logged: the tell-tale message "The runner has received a shutdown signal." no longer appears as a job annotation (which now just says "The operation was canceled.") — it only shows up in the raw job logs. As a result,
observe-aborted-jobs(which grepped annotations) stopped recording these events to CI Analytics.The fix lives in camunda/infra-global-github-actions#744