Skip to content

Issues: bazelbuild/bazel

Release 8.3.0 - June 2025
#25839 opened Apr 14, 2025 by iancha1992
Open 1
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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort

Issues list

code coverage shows 0 when run from bazel test coverage more data needed team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: bug untriaged
#25923 opened Apr 22, 2025 by gpradeepjain
Flip flags for coverage support with remote execution awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally coverage team-Configurability platforms, toolchains, cquery, select(), config transitions team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Remote-Exec Issues and PRs for the Execution (Remote) team
#24927 opened Jan 15, 2025 by fmeum Loading…
Add a note to coverage documentation about GCOV_PREFIX_STRIP on MacOS. awaiting-review PR is awaiting review from an assigned reviewer coverage team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules
#24382 opened Nov 19, 2024 by c-mita Loading…
default GCOV_PREFIX_STRIP value incorrect on macOS coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-CPP Issues for C++ rules type: bug
#23719 opened Sep 23, 2024 by oliverlee
dangling symbolic link with --experimental_fetch_all_coverage_outputs coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-CPP Issues for C++ rules type: bug
#23718 opened Sep 23, 2024 by oliverlee
Bazel coverage collect_coverage.sh Segmentation fault coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules type: support / not a bug (process)
#23476 opened Aug 30, 2024 by kwhitehouse
bazel coverage doesn't produce coverage data for cuda config for XLA. coverage P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: bug
#22709 opened Jun 11, 2024 by hmonishN
Documentation on how to get c++ toolchain to work with bazel converage coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)
#21911 opened Apr 5, 2024 by daivinhtran
LLVM coverage does not process headers which are included via a search path coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-CPP Issues for C++ rules type: bug
#21667 opened Mar 13, 2024 by quuuuux
Bazel Coverage not work in ubuntu 22.04 coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: bug
#20993 opened Jan 23, 2024 by HEffatpanah
bazel coverage with --remote_download_minimal for java_test 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-Java Issues for Java rules type: feature request
#20292 opened Nov 22, 2023 by nlou9
bazel coverage generates a 0-byte coverage file when running a python script coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts team-Rules-Python Native rules for Python type: support / not a bug (process) untriaged
#20233 opened Nov 17, 2023 by BiophiliaSWDA
Questions: Failed to generate .gcda file with bazel coverage in ubuntu coverage more data needed P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules
#20041 opened Nov 3, 2023 by bmeoaountiful
Remote coverage does not have a configuration coverage team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: bug untriaged
#19781 opened Oct 10, 2023 by stevebarrau
Untested C++ files don't impact code coverage awaiting-user-response Awaiting a response from the author coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules type: bug
#19357 opened Aug 29, 2023 by tsr-boxbot
llvm-cov coverage not reporting coverage for header files in the .dat file coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-CPP Issues for C++ rules type: bug
#19338 opened Aug 25, 2023 by carlosgalvezp
Coverage reports are not built reliably coverage P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Rules-Server Issues for serverside rules included with Bazel type: bug
#19098 opened Jul 27, 2023 by UebelAndre
_collect_cc_coverage script can silently fail to produce coverage coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-Server Issues for serverside rules included with Bazel type: bug
#18650 opened Jun 13, 2023 by UebelAndre
[6.2.0] instrumentation_filter doesn't work for bazel coverage with py_test coverage P2 We'll consider working on this in future. (Assignee optional) team-Rules-Server Issues for serverside rules included with Bazel type: bug
#18362 opened May 10, 2023 by nlou9
ProTip! Find all open issues with in progress development work with linked:pr.