You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two scheduled Copilot-engine workflows are failing at runner initialization with:
/bin/bash: line 1: node: command not found
Node.js is not available on PATH when the Copilot CLI engine (GitHub Copilot CLI) tries to start. This is a pre-inference failure — 0 turns and 0 tool calls are recorded in both runs.
Both runs expired their agent job in under 6 minutes with no inference output. No safe_outputs or detection jobs ran.
Root Cause
The Copilot CLI engine requires Node.js to execute. The runner environment for these workflows does not have node on PATH, causing the startup script to fail immediately with exit code 1. This may be due to:
A runner image regression removing Node.js from the default PATH
A missing setup-node step in the compiled lock file
An environment mismatch between the compiled lock file and current runner images
Proposed Remediation
Immediate: Check whether setup-node (or equivalent) is present in daily-news.lock.yml and daily-issues-report.lock.yml — confirm Node.js setup is part of the runner bootstrap
Problem
Two scheduled Copilot-engine workflows are failing at runner initialization with:
Node.js is not available on PATH when the Copilot CLI engine (GitHub Copilot CLI) tries to start. This is a pre-inference failure — 0 turns and 0 tool calls are recorded in both runs.
Affected Workflows
Both runs expired their
agentjob in under 6 minutes with no inference output. Nosafe_outputsordetectionjobs ran.Root Cause
The Copilot CLI engine requires Node.js to execute. The runner environment for these workflows does not have
nodeonPATH, causing the startup script to fail immediately with exit code 1. This may be due to:setup-nodestep in the compiled lock fileProposed Remediation
setup-node(or equivalent) is present indaily-news.lock.ymlanddaily-issues-report.lock.yml— confirm Node.js setup is part of the runner bootstrapSuccess Criteria
node: command not foundnode: command not foundParent Issue
Part of failure investigation report: #27729