Description of the bug:

When running concurrent builds on the same machine using the same repository cache, our build is failing when using the same external repository set by --repository_cache=/repo/shared-bazel-cache :

[INFO 12:20:59.905 src/main/cpp/blaze.cc:2091] failure_detail: message: "error during computation of main repo mapping: error moving repo 
@@some_internal_repo+ into the repo contents cache: /repo/shared-bazel-cache/contents/1cbae686fb9313467fd1c915953a3d0e3a316f8d5ce42de10d6dd677a2878cbc/lock"
external_repository {
}

Which category does this issue belong to?

Core

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Running concurrent builds using the same machine

Which operating system are you running Bazel on?

Rockylinux 8

What is the output of bazel info release?

development version based on 8.3.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

wget https://github.com/bazelbuild/bazel/releases/download/8.3.1/bazel-8.3.1-linux-x86_64 -O /usr/local/bin/bazel 

chmod +x /usr/local/bin/bazel

git clone -b 8.3.1 --single-branch -n https://github.com/bazelbuild/bazel.git /build/bazel
bazel --output_base=/build/cache build //src:bazel $debug

What's the output of git remote get-url origin; git rev-parse HEAD ?

https://github.com/bazelbuild/bazel.git
61aa5a57c5511508a0fd5af8576e541108c0f07d

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response