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

bazel coverage: "Coverage runner: cannot locate file" #7529

Closed
ensonic opened this issue Feb 25, 2019 · 4 comments
Closed

bazel coverage: "Coverage runner: cannot locate file" #7529

ensonic opened this issue Feb 25, 2019 · 4 comments
Labels
coverage P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Java Issues for Java rules type: bug

Comments

@ensonic
Copy link
Contributor

ensonic commented Feb 25, 2019

Description of the problem / feature request:

Generating a test coverage report fails with the error above. It looks like this is the code
https://github.com/bazelbuild/bazel/blob/master/tools/test/collect_coverage.sh#L68
and LCOV_MERGER is empty. Running bazel coverage --combined_report=lcov //... does not help, since it leads to #6450.

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

git clone https://github.com/googlecloudrobotics/core.git
cd core
bazel coverage //...

What operating system are you running Bazel on?

linux (debian)

What's the output of bazel info release?

release 0.22.0

Have you found anything relevant by searching the web?

Nothing on Stackoverflow/Github issues.

@ensonic
Copy link
Contributor Author

ensonic commented Feb 25, 2019

Is something failing to pass the LcovMerger to the env? It looks like this was added here:
werkt@b00c8e7

@iirina
Copy link
Contributor

iirina commented Feb 25, 2019

@ensonic what rule sets do you use? Only the rules embedded by Bazel and that allow coverage collection (Java, C++, shell) have an attribute defined named $lcov_merger. For custom rules the owners have to also define this attribute.

@ensonic
Copy link
Contributor Author

ensonic commented Feb 25, 2019

I just run it against the top of the project, so there is at least python and go. I understand that coverage report is not 100%, but it would be nice to find a better failure mode (eg not run the test rule if the attr is missing?).

@irengrig irengrig added team-Rules-Java Issues for Java rules untriaged labels Mar 1, 2019
@lberki lberki added P2 We'll consider working on this in future. (Assignee optional) coverage and removed untriaged labels Mar 13, 2019
@sgowroji sgowroji added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 16, 2023
@sgowroji
Copy link
Member

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.

@sgowroji sgowroji closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coverage P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Java Issues for Java rules type: bug
Projects
None yet
Development

No branches or pull requests

5 participants