Mark run as Cancelled/Failed upon HostContext.RunnerShutdownToken state

[soelinn]

github/c2c-actions-support#883

• Currently when Actions Runner shuts down for any ShutdownReason, Workflow Run ends as Cancelled.
• ShutdownReason.OperatingSystemShutdown only occurs for Windows platform, and shutdown causes on other platforms are hard to detect accurately.
• Requirement Change
  • ✅ SAME: User Cancellation from the GitHub UI remains the same ➡️ TaskResult.Cancelled.
  • ⚠️ CHANGE: Mark Workflow Run as TaskResult.Failed after receiving a runner shutdown signal (e.g., SIGTERM)
    • This TaskResult.Failed state can only be occur if the Runner process can report its shutdown state back to the Actions Service successfully before exiting.
    • I coded this behavior change by depending on the HostContext.RunnerShutdownToken.IsCancellationRequested when the Runner process receives a Ctrl-C or Ctrl-Break signal. It will only be able to report back to the Actions Service upon SIGTERM as SIGKILL will be immediate, and won't allow graceful shutdown.
  • If Runner process exiting due to Ctrl-C SIGTERM by user manually ➡️ TaskResult.Failed

[TingluoHuang]

FYI, you might only get OperatingSystemShutdown when you are on Windows and configure the runner as a Windows service.

[soelinn]

I expected it'll be cases like this, and I might not be able to handle it reliably and distinguish between UserCancellation vs OS shutdown. I will probably need to consult @chrispat.