fix: prevent sticky disk commit after buildkitd SIGKILL

Add an in-memory _sigkillUsed flag alongside the existing core.saveState
persistence. This ensures getSigkillUsed() returns true within the same
process even if the GitHub Actions state mechanism has issues during
post-action cleanup.

Also log a warning (instead of the misleading 'gracefully') when
buildkitd was actually terminated with SIGKILL.

Co-authored-by: Codesmith <codesmith@blacksmith.sh>

Author: adityamaru

dist/index.js

@@ -707,7 +707,11 @@ void actionsToolkit.run(
               Metric_MetricType.BPA_BUILDKITD_SHUTDOWN_DURATION_MS,
               buildkitdShutdownDurationMs,
             );
-            core.info("Shutdown buildkitd gracefully");
+            if (stateHelper.getSigkillUsed()) {
+              core.warning("buildkitd was terminated with SIGKILL after graceful shutdown failed");
+            } else {
+              core.info("Shutdown buildkitd gracefully");
+            }
           } else {
             // Check if buildkitd was expected to be running (we have state indicating it was started)
             const buildkitdAddr = stateHelper.getBuildkitdAddr();

dist/index.js.map

@@ -38,10 +38,13 @@ export function getBuilderName(): string {
   return core.getState("builderName");
 }
 
+let _sigkillUsed = false;
+
 export function setSigkillUsed(used: boolean) {
+  _sigkillUsed = used;
   core.saveState("sigkillUsed", used.toString());
 }
 
 export function getSigkillUsed(): boolean {
-  return core.getState("sigkillUsed") === "true";
+  return _sigkillUsed || core.getState("sigkillUsed") === "true";
 }