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

No coverage files when running a build with --remote_download_minimal or --remote_download_toplevel #12592

Closed
Tracked by #12665
arjantop-cai opened this issue Dec 1, 2020 · 2 comments
Assignees
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug

Comments

@arjantop-cai
Copy link

Description of the problem / feature request:

I am not sure if this is the desired behavior (especially for minimal) or a bug.

Running bazel coverage (with 100% cache hit rate) and --remote_download_minimal does not download coverage files. Configured --coverage_report_generator logs are visible in the output but it seems like the generator is not actually run.
As a result no output coverage file is produced and there are no coverage files present in the test output.

Sample output of configured --coverage_report_generator, ran today (December 1st) but logs are from November 27th (from cache):

{"level":"info","ts":1606483666.4905822,"caller":"coverage/coverage.go:48","msg":"Collecting coverage","path":"bazel-out/k8-fastbuild-ST-fcb5cf22ec9a/testlogs/foo/bar/go_default_test/coverage.dat"}

Google Cloud storage is used as a remote cache (if this could have any impact).

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

Run bazel coverage where the cache hit is 100%, coverage files are not downloaded.

What operating system are you running Bazel on?

MacOS Catalina 10.15.7

What's the output of bazel info release?

release 3.6.0
@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 19, 2023
@coeuvre
Copy link
Member

coeuvre commented Apr 19, 2023

Should be fixed by #16556.

@coeuvre coeuvre closed this as completed Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug
Projects
None yet
Development

No branches or pull requests

3 participants