Skip to content

Bazel does not re-evaluate remote actions, even after shutdown #17366

@ozio85

Description

@ozio85

Description of the bug:

Currently Bazel does not re-evaluate remote actions towards the remote execution service, even after a shutdown is performed.

This causes errors when:

  1. The remote cache rotates
  2. The remote cache is completely wiped.

This leads to a:
(Exit 34): /home/path/to/file.h (No such file or directory)
(BulkTransferException)

And before this could be reparied by rerunning (since this error causes bazel to shutdown). But the behavior now is even after restart, Bazel still remembers the state, and the BulkTransferException remains until a bazel clean is performed

I am using:
--remote_download_toplevel

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

bazel build //something --experimental_remote_grpc_log=first.run.log

bazel shutdown

bazel build //something --experimental_remote_grpc_log=second.run.log

I expect bazel to reevaluate the actions towards the remote server, to see if any needs a re-run.

Which operating system are you running Bazel on?

linux

What is the output of bazel info release?

7.0.0-pre.20221111.3

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?

This is the same issue as #13882, however in 7.0.0, it is enabled by default
How is this ever going to work?

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

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions