Bazel crash #27892
Description
Description of the bug:
WARNING: Failed to delete contents of sandbox /private/var/tmp/_bazel_lmirelmann/f79d10c4ea92f8b594300dbedaa3ff9d/sandbox: java.io.IOException: /private/var/tmp/_bazel_lmirelmann/f79d10c4ea92f8b594300dbedaa3ff9d/sandbox/darwin-sandbox (Directory not empty)
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.IllegalStateException: Found unexpected entries in sandbox base. Please report this in https://github.com/bazelbuild/bazel/issues. The entries are: _moved_trash_dir, darwin-sandbox, sandbox_stash
at com.google.devtools.build.lib.sandbox.SandboxModule.checkSandboxBaseTopOnlyContainsPersistentDirs(SandboxModule.java:573)
at com.google.devtools.build.lib.sandbox.SandboxModule.afterCommand(SandboxModule.java:611)
at com.google.devtools.build.lib.runtime.BlazeRuntime.afterCommand(BlazeRuntime.java:734)
at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.execExclusively(BlazeCommandDispatcher.java:711)
at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.exec(BlazeCommandDispatcher.java:257)
at com.google.devtools.build.lib.server.GrpcServerImpl.executeCommand(GrpcServerImpl.java:607)
at com.google.devtools.build.lib.server.GrpcServerImpl.lambda$run$0(GrpcServerImpl.java:677)
at io.grpc.Context$1.run(Context.java:566)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
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.
Was not able to reproduce this, this happened while compiling a C++ project
Which operating system are you running Bazel on?
MacOS
What is the output of bazel info release?
release 8.4.2
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse HEAD ?
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
This was a one-of, not able to reproduce this.
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response