Skip to content

--remote_download_minimal does not work with --build_event_publish_all_actions #10971

@scele

Description

@scele

Description of the problem / feature request:

--remote_download_minimal does not work with --build_event_publish_all_actions.

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

$ cat BUILD 
cc_binary(
    name = "test",
    srcs = ["test.cc"],
)
$ cat test.cc 
int main() {
    return 1;
}
# First, make sure that all actions are populated in the remote cache
# I'm using buildbarn, but I don't think this is related to the remote cache implementation.
bazel build ... --remote_cache=grpc://127.0.0.1:8980 --remote_instance_name=local --remote_upload_local_results=true
# Then, clean to ensure that remote_download_minimal is kicking in.
bazel clean
# Observe a failure from writing build events.
bazel build ... --remote_cache=grpc://127.0.0.1:8980 --remote_instance_name=local --remote_upload_local_results=true --remote_download_minimal --build_event_json_file=$PWD/be.json --build_event_publish_all_actions
INFO: Invocation ID: 87151a7b-6ca0-4c26-9ced-b4534bd969e9
INFO: Analyzed target //:test (13 packages loaded, 47 targets configured).
INFO: Found 1 target...
INFO: Deleting stale sandbox base /mnt/data2/cache/bazel/_bazel_lpeltonen/1da3da6443024d4847298a76d6f71841/sandbox
Target //:test up-to-date:
  bazel-bin/test
INFO: Elapsed time: 3.285s, Critical Path: 0.98s
INFO: 2 processes: 2 remote cache hit.
ERROR: Unable to write all BEP events to file due to 'java.io.FileNotFoundException: /mnt/data2/cache/bazel/_bazel_lpeltonen/1da3da6443024d4847298a76d6f71841/execroot/__main__/bazel-out/k8-fastbuild/bin/_objs/test/test.pic.o (No such file or directory)'
INFO: Build completed successfully, 5 total actions

What operating system are you running Bazel on?

Ubuntu 18.04.

What's the output of bazel info release?

release 2.2.0

Also reproduces on recent master (3c89a91).

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

git@github.com:bazelbuild/bazel.git
3c89a910ad1c59160ba4058c47b6752ce9e7efb6
3c89a910ad1c59160ba4058c47b6752ce9e7efb6

Have you found anything relevant by searching the web?

No.

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

I think I understand what the issue is, I have opened #10972 that shows one way to fix the issue.

Metadata

Metadata

Assignees

Labels

P2We'll consider working on this in future. (Assignee optional)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