Description of the bug:

We've discovered some builds, hanging on "Compiling Java headers" for indefinite state in remote execution. Hacking around and passing some kill -3 commands to bazel in our runner I've discovered that there are two skyframe-evaluator threads sitting in blockingAwait() in com.google.devtools.build.lib.remote.RemoteExecutionCache.ensureInputsPresent(RemoteExecutionCache.java:115) (I've attached a full thread dump below).

It is always Compiling Java headers stuck, and always two skyframe-evaluator threads sitting on this line (e.g. skyframe-evaluator 357 and skyframe-evaluator 490 in attached thread dump.

I still in doubt if it is caused by some infrastructure failure, by problem with remote executor (tested on buildbarn) or by some of tons of flags which we are using in our build configuration.

I've tried to remove those flags, to enable build profile, to disable build profile, still don't luck.

Couldn't insist that it is some kind of race condition in RemoteExecutionCache, but "looks like it is".

We are using 6.0.0-pre.20220922.1, and as for now could not downgrade to test if such behaviour present in lower versions.

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

No response

Which operating system are you running Bazel on?

linux

What is the output of bazel info release?

release 6.0.0-pre.20220922.1

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 master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

There are no similar issues on these resources

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

bazel-server.jvm.threaddump.txt