Feature #8704
closed
Support processing of multiple error traces per one unsafe report
Added by Pavel Andrianov about 6 years ago.
Updated almost 6 years ago.
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.
- 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
- Blocked by Feature #8705: Change the way of reporting unsafe reports added
- 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.
- Status changed from New to Feedback
- % Done changed from 0 to 100
Implemented in "new-report-data".
- 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
Moreover, I suggest to specify in errors what particular attribute values were redefined.
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.
- Status changed from Open to Resolved
Seems to be resolved some time ago in branch new-report-data.
- Status changed from Resolved to Closed
I merged the branch to master in 4339da97 as a part of branch core-new-formats.
- Related to Feature #9414: Reuse archive with source files between different error traces on report uploading added
Also available in: Atom
PDF