Feature #8704: Support processing of multiple error traces per one unsafe report - Klever - Open-Source Projects

Actions

Copy link

Feature #8704

closed

Support processing of multiple error traces per one unsafe report

Added by Pavel Andrianov almost 7 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Urgent

Assignee:

Vladimir Gratinskiy

Category:

Bridge

Target version:

1.0

Start date:

02/06/2018

Due date:

% Done:

100%

Estimated time:

Published in build:

Description

To reduce amount of uploaded sources and the total number of reports it is needed to process multiple error traces per one unsafe report (the corresponding format described in the specification). The key feature: not to save total amount of sources for every error trace in report, but to save all related sources for all error traces of a given unsafe report once.

Related issues 3 (0 open — 3 closed)

Actions

Copy link

Updated by Evgeny Novikov almost 7 years ago

Subject changed from Implement new report format to Support processing of multiple error traces per one unsafe report
Description updated (diff)
Assignee set to Vladimir Gratinskiy
Priority changed from Normal to Urgent
Target version set to 2.0

Actions

Copy link

Updated by Evgeny Novikov almost 7 years ago

Blocked by Feature #8705: Change the way of reporting unsafe reports added

Actions

Copy link

Updated by Evgeny Novikov almost 7 years 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.

Actions

Copy link

Updated by Evgeny Novikov almost 7 years ago

Related to Feature #8570: Introduce data attributes added

Actions

Copy link

Updated by Vladimir Gratinskiy over 6 years ago

Status changed from New to Feedback
% Done changed from 0 to 100

Implemented in "new-report-data".

Actions

Copy link

Updated by Evgeny Novikov over 6 years ago

Status changed from Feedback to Open

When I try to upload an unsafe report with multiple error traces where each error trace includes:

    "attrs": [
        {
            "associate": true,
            "compare": true,
            "name": "Error trace identifier",
            "value": "$UNIQUE_VALUE" 
        }
    ]

I gets the following error from Bridge:

Uploading report failed: attributes were redefined
Traceback (most recent call last):
  File "/home/novikov/work/klever/bridge/reports/UploadReport.py", line 72, in __init__
    self.__upload()
  File "/home/novikov/work/klever/bridge/reports/UploadReport.py", line 326, in __upload
    raise ValueError("attributes were redefined")
ValueError: attributes were redefined

Actions

Copy link

Updated by Evgeny Novikov over 6 years ago

Moreover, I suggest to specify in errors what particular attribute values were redefined.

Actions

Copy link

Updated by Evgeny Novikov over 6 years ago

Now Bridge does not fail, but it still does not properly handle error trace attributes, namely, it neither shows them nor use them for verification results comparison and error trace patterns matching although I set corresponding parameters within these attributes.

Actions

Copy link