Skip to content

--bes_timeout is ignored in Bazel 5 #14576

@BalestraPatrick

Description

@BalestraPatrick

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 git@github.com: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

Metadata

Metadata

Assignees

Labels

P1I'll work on this now. (Assignee required)team-Remote-ExecIssues and PRs for the Execution (Remote) teamtype: bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions