Project

General

Profile

Feature #8704

Support processing of multiple error traces per one unsafe report

Added by Pavel Andrianov about 1 year ago. Updated 9 months ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
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

Related to Klever - Feature #8570: Introduce data attributesClosed2017-11-13

Related to Klever - Feature #9414: Reuse archive with source files between different error traces on report uploadingOpen2019-01-25

Blocked by Klever - Feature #8705: Change the way of reporting unsafe reportsClosed2018-02-06

History

#1 Updated by Evgeny Novikov about 1 year ago

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

#2 Updated by Evgeny Novikov about 1 year ago

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

#3 Updated by Evgeny Novikov 11 months 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.

#4 Updated by Evgeny Novikov 11 months ago

#5 Updated by Vladimir Gratinskiy 9 months ago

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

Implemented in "new-report-data".

#6 Updated by Evgeny Novikov 9 months 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

#7 Updated by Evgeny Novikov 9 months ago

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

#8 Updated by Evgeny Novikov 9 months 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.

#9 Updated by Evgeny Novikov 9 months ago

  • Status changed from Open to Resolved

Seems to be resolved some time ago in branch new-report-data.

#10 Updated by Evgeny Novikov 9 months ago

  • Status changed from Resolved to Closed

I merged the branch to master in 4339da97 as a part of branch core-new-formats.

#11 Updated by Vitaly Mordan 2 months ago

  • Related to Feature #9414: Reuse archive with source files between different error traces on report uploading added

Also available in: Atom PDF