Description of the bug:

We noticed that Bazel occasionally (about 5% in our env) fails due to linux-sandbox not being available.

ERROR: 'linux-sandbox' was requested for default strategies but no strategy with that identifier was registered. Valid values are: [processwrapper-sandbox, standalone, remote, worker, sandboxed, local]

It seems that recently a 1s timeout was introduced in checking if linux-sandbox available #15414, which might be too tight under load.

In our setup, we disable all other weaker sandboxes for hermeticity, which makes this fail reliably and easy to notice. I suspect this is happening on more environments, but people haven't noticed because ofprocesswrapper-sandbox fallback.

CC @meisterT

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

run Bazel >=6.0.0 with --spawn_strategy=worker,linux-sandbox under a heavy load many times.

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

No response

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?

No response

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

No response