bazelbuild / bazelbuild/bazel

Reduce logging for coverage invocations

Open
#16,031 6 comments 1 reaction 0 assignees View on GitHub
coverage P3 team-Rules-Server type: feature request
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the feature request:

Whenever I run coverage I get a massive log that's largely

```
File '/foo/bar.h'
Lines executed0.00% of 3

File '/foo/baz.h'
No executable lines

File '/foo/qux.h'
Lines executed0.00% of 3
```

Would it be possible to disable these by default or at least provide a flag to reduce nose?

### What underlying problem are you trying to solve with this feature?

I would like to maintain the readability of my logs while using coverage builds.

### Which operating system are you running Bazel on?

Linux

### What is the output of `bazel info release`?

release 5.2.0

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by tracing the coverage invocation that emits the File, Lines executed, and No executable lines records, then identify where its verbosity is configured. Done should mean coverage builds provide the requested quieter default or explicit control without obscuring useful results; verify the behavior on Linux with Bazel 5.2.0.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.