Bazel CI: tests tagged as "block-network" fail on macOS

Description of the problem / feature request:

Bazel’s own tests that are tagged as “block-network” now fail on macOS when testing with Bazel built from HEAD, but work when testing with Bazel 1.2.1.

Bugs: what’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Edit //src/test/shell/bazel/workspace_resolved_test.sh, and remove every test method. Add a test method that just runs bazel info, then test. Witness this error in the log:

Server crashed during startup. Now printing /private/var/tmp/_bazel_buildkite/0f6cf1b347f184bdf59fc3dbd70d52bf/sandbox/darwin-sandbox/4257/execroot/io_bazel/_tmp/81731060611f1135fb37d82b4c16c3ce/root/0776a7d52f698afa6331a0f743d059a6/server/jvm.out
I/O Error: Failed to bind
-- Test log: -----------------------------------------------------------
------------------------------------------------------------------------

Update: culprit is 8e7c3494831edba5fef8a29d200d3b63fc282e46

What operating system are you running Bazel on?

macOS Catalina (10.15.1)

What’s the output of bazel info release?

Using Bazel built at 5be24a81ff374ab7690ef08a933501f6eaf05efe

[philwo]

@ngeor Could you please file a new issue and add log output etc.? This makes it easier for us to prioritize and handle it than a comment on an old and already closed issue. Feel free to reference this one as a prior occurrence, of course! Thank you 😊

[ngeor]

Hi folks,

I seem to have stumbled upon this issue with Bazel 5.0 and macOS Monterey 12.2.1

Only on Mac, unit tests that try to listen on localhost are failing with “block-network”.

They pass fine on CI (Linux).