Project

General

Profile

Feature #8705

Change the way of reporting unsafe reports

Added by Evgeny Novikov over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Urgent
Category:
Results processing
Target version:
Start date:
02/06/2018
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment Klever Core reports one unsafe report per each error trace, but this is absolutely inefficient when many error traces are issued for one invocation of a static verifier, because of almost the same sources are packed and uploaded multiple times and there are too many useless reports. We supposed to report all error traces and all sources once for one invocation of a static verifier.


Related issues

Related to Klever - Bug #9067: Klever fails with corruptedClosed07/05/2018

Actions
Blocks Klever - Feature #8704: Support processing of multiple error traces per one unsafe reportClosed02/06/2018

Actions

History

#1

Updated by Evgeny Novikov over 1 year ago

  • Target version changed from 1.0 to 2.0
#2

Updated by Evgeny Novikov over 1 year ago

  • Blocks Feature #8704: Support processing of multiple error traces per one unsafe report added
#3

Updated by Evgeny Novikov over 1 year ago

  • Target version changed from 2.0 to 1.0

Let's hurry up this issue, since it is very high demanded, so, waiting for Klever 2.0 isn't good.

BTW, I extended the version period appropriately to have enough time for implementation and testing.

#4

Updated by Evgeny Novikov about 1 year ago

  • Assignee changed from Ilja Zakharov to Evgeny Novikov
  • Status changed from New to Resolved

I did it in branch core-new-formats. But Bridge doesn't accept unsafe reports with multiple error traces. Let's find out who is wrong.

#5

Updated by Evgeny Novikov about 1 year ago

  • Status changed from Resolved to Closed

I merged the branch to master in 4339da97.

#6

Updated by Evgeny Novikov 12 months ago

  • Related to Bug #9067: Klever fails with corrupted added

Also available in: Atom PDF