[8.3.0] Fix the issue with duplicate work request IDs (bazelbuild#26285)

Fixes bazelbuild#26251.

Closes bazelbuild#26269.

PiperOrigin-RevId: 770671688
Change-Id: Ie43adaea98377ea92cfb38b55f25d9e034c179de

Commit
bazelbuild@7319e5e

Co-authored-by: Jaden Peterson <[email protected]>

Author: iancha1992

src/main/java/com/google/devtools/build/lib/worker/WorkerSpawnRunner.java

@@ -91,13 +91,20 @@ final class WorkerSpawnRunner implements SpawnRunner {
   private static final int VERBOSE_LEVEL = 10;
 
   private final SandboxHelpers helpers;
+  /**
+   * The next work request ID to use. This field is static so we don't reuse work request IDs across
+   * Bazel invocations. Although that shouldn't happen under normal circumstances because we wait
+   * until a request finishes before exiting, it can happen if dynamic execution is enabled and one
+   * branch beats the other in the race.
+   */
+  private static final AtomicInteger requestIdCounter = new AtomicInteger(1);
+
   private final Path execRoot;
   private final ExtendedEventHandler reporter;
   private final ResourceManager resourceManager;
   private final RunfilesTreeUpdater runfilesTreeUpdater;
   private final WorkerOptions workerOptions;
   private final WorkerParser workerParser;
-  private final AtomicInteger requestIdCounter = new AtomicInteger(1);
   private final WorkerProcessMetricsCollector metricsCollector;
 
   public WorkerSpawnRunner(