Remove the preconditions check that an action is not running when accessing its aggregated elapsed time.

It may have transitioned back to running if it was rewound. In this case, using the completed execution's aggregated elapsed time seems reasonable.

PiperOrigin-RevId: 391572822

src/main/java/com/google/devtools/build/lib/runtime/CriticalPathComponent.java

diff --git a/src/main/java/com/google/devtools/build/lib/runtime/CriticalPathComponent.java b/src/main/java/com/google/devtools/build/lib/runtime/CriticalPathComponent.java
index 2fed7c7..e3600f1 100644
--- a/src/main/java/com/google/devtools/build/lib/runtime/CriticalPathComponent.java
+++ b/src/main/java/com/google/devtools/build/lib/runtime/CriticalPathComponent.java
@@ -235,7 +235,7 @@
    */
   synchronized void addDepInfo(CriticalPathComponent dep, long componentFinishNanos) {
     long currentElapsedTime = componentFinishNanos - startNanos;
-    long aggregatedElapsedTime = dep.getAggregatedElapsedTimeNanos() + currentElapsedTime;
+    long aggregatedElapsedTime = dep.aggregatedElapsedTime + currentElapsedTime;
     // This corrects the overlapping run time.
     if (dep.finishNanos > startNanos) {
       aggregatedElapsedTime -= dep.finishNanos - startNanos;
@@ -289,12 +289,7 @@
    * <p>Critical path is defined as : action_execution_time + max(child_critical_path).
    */
   Duration getAggregatedElapsedTime() {
-    return Duration.ofNanos(getAggregatedElapsedTimeNanos());
-  }
-
-  private long getAggregatedElapsedTimeNanos() {
-    Preconditions.checkState(!isRunning, "Still running %s", this);
-    return aggregatedElapsedTime;
+    return Duration.ofNanos(aggregatedElapsedTime);
   }
 
   /**