Project

General

Profile

Actions
Copy link

Bug #10838

closed

Properly show completely non-covered files of verificatioin tasks

Added by Evgeny Novikov over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Vladimir Gratinskiy
Category:
Bridge
Target version:
3.3
Start date:
05/13/2021
Due date:
08/30/2021
% Done:

100%

Estimated time:
Detected in build:
git
Platform:
Published in build:

Description

Now Bridge shows completely non-covered files of verification tasks as "0/0" (line coverage) and "0/0" (function coverage) that is it excludes corresponding line and function numbers from statistics.

Actions
Copy link
 #1

Updated by Evgeny Novikov over 3 years ago

  • Status changed from New to Resolved

It was fixed in branch bridge-fixes commit b9f2880. The fix requires migration and recalculation of the code coverage cache for all jobs.

Actions
Copy link
 #2

Updated by Evgeny Novikov over 3 years ago

  • Status changed from Resolved to Open

We revealed that Core provides to Bridge incomplete data so that Bridge could not calculate and show code coverage well enough both for verification tasks and in total. The slightly changed format of code coverage reports should fix the issue.

Actions
Copy link
 #3

Updated by Evgeny Novikov over 3 years ago

  • Target version changed from 3.2 to 3.3

Though Vladimir fixed the issue for newly obtained code coverage reports, but Bridge needs to support previously got ones. Without this they will look very bad.

Actions
Copy link
 #4

Updated by Vladimir Gratinskiy about 3 years ago

  • Due date set to 08/30/2021
  • Status changed from Open to Resolved
  • % Done changed from 0 to 100

"Migration" was added in "bridge-fixes" - new button on a secret page that fixes old global coverage archives.

Actions
Copy link
 #5

Updated by Evgeny Novikov about 3 years ago

  • Status changed from Resolved to Closed

This is a great fix of a quite old bug! I merged the branch to master in 0cde276bc. If you will update an existing Klever instance, you will need to visit page "/tools/secret/" once and a press the only button there to migrate old code coverage reports (don't expect that invalid data will be fixed up anyhow, but at least you will have a pretty good visualization of total code coverage reports). Also, you should recalculate the code coverage cache for all/interesting verification jobs.

Actions
Copy link

Also available in: Atom PDF