Klever

This issue is not strictly bound with purposes of 2.0 that targets verification of C software.

Let's Vladimir will do this after his vacation.

Implemented in bridge-2.0

I see a new column for a table with unsafe marks, but not for a table with unsafes, where it is more required.

Tests passed, so, I merged the branch to master in b8bda00ac.

For the attached job I still do not see total similarities in tables with unsafes.

Also, please, visualize similarities using percents rather than floats like for associated marks/unsafes at unsafe/mark pages.

Evgeny Novikov wrote:

For the attached job I still do not see total similarities in tables with unsafes.

Also, please, visualize similarities using percents rather than floats like for associated marks/unsafes at unsafe/mark pages.

Fixed.

Looks nice. I cherry picked the commit to master 2c6ef7e55.

I found out one more issue. Bridge always shows total similarity <= 100% in the unsafe marks table even for marks with several associated reports. At least before when downloading JSON files with results total similarities were summed up, e.g. when there are 3 associated unsafes each with 100% similarity there was 300% total similarity or 3.0. I would like to have this behavior everywhere since it is strange to see total similarity 50% for a mark associated with 2 unsafes (one with 100% and another with 0%).

I think more about this. Indeed the current representation is better, as one can easily detect partially associated marks even when there are several unsafes per a mark.

For downloaded JSON files it is better to remain everything as it was before implementation of this feature if something changed.