New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 844162 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 845735



Sign in to add a comment

LLVM: implement a new representation for coverage data

Project Member Reported by mmoroz@chromium.org, May 17 2018

Issue description

The format needs to be lightweight and fast to process, but at the same time sufficient for rendering coverage report given a coverage data in that new format + source code text.

I have some ideas, will give it a shot once we resolve current high priority action items.
 

Comment 1 by mmoroz@chromium.org, May 17 2018

Cc: flyboy@chromium.org aga...@chromium.org

Comment 2 by mmoroz@chromium.org, May 18 2018

Reminder to myself: template instantiations can be tricky to serialize / deserialize.

Comment 3 by mmoroz@chromium.org, May 22 2018

Blocking: 845735

Comment 4 by mmoroz@chromium.org, May 23 2018

For a complete awesomeness, that format must support merge. That way, we should be able to merge reports generated for different platforms / build configurations.

Comment 5 by mmoroz@chromium.org, Jun 13 2018

Note to future myself: keep in mind that the format should be language independent, e.g. if someone implements coverage for Java, they should be able to produce file in that format and the same rendering pipeline needs to be able to render both C/C++ and Java.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Owner: st...@chromium.org
Shuotao, do you want to be an owner of this, as you've started working on https://chromium-review.googlesource.com/c/infra/infra/+/1292333 ?

Sure. The format I defined is pretty extensible.

Sign in to add a comment