Bug #7250
closed
Bridge fails on comparing 2 reports
Added by Vitaly Mordan almost 8 years ago.
Updated over 7 years ago.
Description
How to reproduce:
http://ldvstore:8998/jobs/
compare reports
236fdf8c6faa4c1b414fc81c56a54080 (MAVBT, internal, L1) and
d7e357583ed9e067b908be73e8dad4fe (SBT, property automaton)
or
28e46542c54572bff4332313e385fa0c (Crypto, SBT) and
18279c73ec1829e5f171179776eb0069 (Crypto, MAV, L1/L2)
leads to the following error message:
"Unknown error while filling comparison cache"
- Subject changed from Klever fails on comparing 2 reports to Bridge fails on comparing 2 reports
- Assignee changed from Evgeny Novikov to Vladimir Gratinskiy
- Priority changed from Normal to High
As far as I know, you can upload several unsafe reports connected to the same verification report that corresponds to the unique pair of the verification object and rule specification. Do you distinguish these unsafe reports, e.g. by additional attributes like bug kinds?
Anyway Bridge should provide more information on errors.
Evgeny Novikov wrote:
Anyway Bridge should provide more information on errors.
Log provides more information.
- Priority changed from High to Normal
Let's postpone this issue until a new approach for checking requirements will be implemented.
- Status changed from New to Resolved
I believe this issue is resolved, since Bridge now can compare reports.
- Status changed from Resolved to Rejected
- Assignee deleted (
Vladimir Gratinskiy)
Nobody analyzed this issue.
Also available in: Atom
PDF