Description of the problem / feature request:
--bes_timeout doesn't seem to be respected anymore in Bazel 5.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
This will complete successfully and upload the full BES even though it shouldn't because the timeout is set to a very low 1ms:
$ git clone [email protected]:bazelbuild/rules_apple.git
$ cd rules_apple
$ env USE_BAZEL_VERSION=5.0.0rc4 bazelisk build --remote_cache=grpcs://remote.buildbuddy.io --bes_backend=grpcs://remote.buildbuddy.io --bes_results_url=https://app.buildbuddy.io/invocation/ //examples/iOS/StickersApp --bes_timeout=1ms --cpu=ios_x86_64
While this will fail as expected in Bazel 4.2.1:
$ env USE_BAZEL_VERSION=4.2.1 bazelisk build --remote_cache=grpcs://remote.buildbuddy.io --bes_backend=grpcs://remote.buildbuddy.io --bes_results_url=https://app.buildbuddy.io/invocation/ //examples/iOS/StickersApp --bes_timeout=1ms --cpu=ios_x86_64
ERROR: The Build Event Protocol upload timed out. com.google.common.util.concurrent.TimeoutFuture$TimeoutFutureException: Timed out: com.google.common.util.concurrent.Futures$NonCancellationPropagatingFuture@43553e48[status=PENDING, info=[delegate=[com.google.common.util.concurrent.SettableFuture@4d92c852[status=PENDING]]]]
What operating system are you running Bazel on?
Replace this line with your answer.
macOS 12.1
Description of the problem / feature request:
--bes_timeoutdoesn't seem to be respected anymore in Bazel 5.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
This will complete successfully and upload the full BES even though it shouldn't because the timeout is set to a very low 1ms:
While this will fail as expected in Bazel 4.2.1:
What operating system are you running Bazel on?
macOS 12.1