-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Enable coverage for generated source files #11375
Copy link
Copy link
Closed as not planned
Labels
P4This is either out of scope or we don't have bandwidth to review a PR. (No assignee)This is either out of scope or we don't have bandwidth to review a PR. (No assignee)staleIssues or PRs that are stale (no activity for 30 days)Issues or PRs that are stale (no activity for 30 days)team-Rules-ServerIssues for serverside rules included with BazelIssues for serverside rules included with Bazeltype: feature request
Description
Description of the problem / feature request:
Currently when using coverage all generated source files are ignored. The files neither show up in source file manifest nor do they have a baseline coverage. I would like to enable to get coverage for generated source files as this not currently possible.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Have a generated source file as a source to a rule.
What operating system are you running Bazel on?
Ubuntu 19.10
What's the output of bazel info release?
release 3.1.0
Have you found anything relevant by searching the web?
No.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P4This is either out of scope or we don't have bandwidth to review a PR. (No assignee)This is either out of scope or we don't have bandwidth to review a PR. (No assignee)staleIssues or PRs that are stale (no activity for 30 days)Issues or PRs that are stale (no activity for 30 days)team-Rules-ServerIssues for serverside rules included with BazelIssues for serverside rules included with Bazeltype: feature request