Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build event file creation fails with coverage and remote-cache #12013

Closed
lizan opened this issue Aug 27, 2020 · 2 comments
Closed

Build event file creation fails with coverage and remote-cache #12013

lizan opened this issue Aug 27, 2020 · 2 comments
Labels
coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Server Issues for serverside rules included with Bazel type: bug

Comments

@lizan
Copy link

lizan commented Aug 27, 2020

Description of the problem / feature request:

using bazel coverage with --build_event_json_file fails with:
ERROR: Unable to write all BEP events to file due to 'java.io.FileNotFoundException: /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-fastbuild/testlogs/test/common/common/statusor_test/baseline_coverage.dat (No such file or directory)'

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

https://dev.azure.com/cncf/envoy/_build/results?buildId=49206&view=logs&j=724db6ef-a27f-5b54-bc41-0e2ad1c5e0c3&t=228179bb-5fc5-500b-1a8a-a25f640ced89

In Envoy repo run any test with coverage, build_event_json_file and use remote-cache.

What operating system are you running Bazel on?

Ubuntu 18.04

What's the output of bazel info release?

release 3.4.1

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

https://github.com/envoyproxy/envoy.git
6c0b368e2df27c3c6c42690bd5bf4c0b8816473c
6c0b368e2df27c3c6c42690bd5bf4c0b8816473c

Have you found anything relevant by searching the web?

Might related #11942

lizan added a commit to lizan/envoy that referenced this issue Aug 27, 2020
Turns out it doesn't work with remote cache and coverage.
bazelbuild/bazel#12013

With this we can enable S3 cache for ARM and coverage builds.

Signed-off-by: Lizan Zhou <[email protected]>
lizan added a commit to envoyproxy/envoy that referenced this issue Aug 28, 2020
Turns out it doesn't work with remote cache and coverage.
bazelbuild/bazel#12013

With this we can enable S3 cache for ARM and coverage builds.

Signed-off-by: Lizan Zhou <[email protected]>
@oquenchil oquenchil added team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug untriaged coverage team-Rules-Server Issues for serverside rules included with Bazel and removed team-Remote-Exec Issues and PRs for the Execution (Remote) team labels Aug 28, 2020
clarakosi pushed a commit to clarakosi/envoy that referenced this issue Sep 3, 2020
Turns out it doesn't work with remote cache and coverage.
bazelbuild/bazel#12013

With this we can enable S3 cache for ARM and coverage builds.

Signed-off-by: Lizan Zhou <[email protected]>
Signed-off-by: Clara Andrew-Wani <[email protected]>
@lberki lberki added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed untriaged labels Nov 18, 2020
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Apr 12, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Server Issues for serverside rules included with Bazel type: bug
Projects
None yet
Development

No branches or pull requests

3 participants