Handle very quick preemptions correctly on GCP Batch [AN-274]

broadinstitute · Feb 11, 2025 · 847c137 · 847c137
1 parent 648f65a
commit 847c137
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/...batch/src/main/scala/cromwell/backend/google/batch/api/request/BatchRequestExecutor.scala b/...batch/src/main/scala/cromwell/backend/google/batch/api/request/BatchRequestExecutor.scala
@@ -28,8 +28,9 @@ trait BatchRequestExecutor {
 }
 
 object BatchRequestExecutor {
+  // The "from" state is *usually* RUNNING, but if a VM is quickly preempted it could be an earlier state like PENDING.
   private val VM_PREEMPTION_PATTERN = Pattern.compile(
-    "failed due to the following task event: \"Task state is updated from RUNNING to FAILED on zones/\\S+ due to Spot VM preemption with exit code 50001.\""
+    "failed due to the following task event: \"Task state is updated from \\S+ to FAILED on zones/\\S+ due to Spot VM preemption with exit code 50001.\""
   )
 
   class CloudImpl(batchSettings: BatchServiceSettings) extends BatchRequestExecutor with LazyLogging {