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

Enable coverage for generated source files #11375

Closed
Rasrack opened this issue May 13, 2020 · 4 comments
Closed

Enable coverage for generated source files #11375

Rasrack opened this issue May 13, 2020 · 4 comments
Labels
P4 This is either out of scope or we don't have bandwidth 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: feature request

Comments

@Rasrack
Copy link
Contributor

Rasrack commented May 13, 2020

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.

@jin jin added team-Rules-Server Issues for serverside rules included with Bazel untriaged labels May 13, 2020
@lberki lberki added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: feature request and removed untriaged labels Nov 18, 2020
@c-mita c-mita linked a pull request Nov 3, 2021 that will close this issue
@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
@Rasrack
Copy link
Contributor Author

Rasrack commented Apr 12, 2023

@c-mita can you mark it as at "not-stale" whilest awaiting #11350?

@sgowroji sgowroji removed the stale Issues or PRs that are stale (no activity for 30 days) label Apr 12, 2023
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 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.

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

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post @bazelbuild/triage in a comment here and we'll take a look. Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 This is either out of scope or we don't have bandwidth 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: feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants