Project

General

Profile

Actions
Copy link

Bug #8449

closed

Verification reports do not have computational resources in the lightweight mode

Added by Evgeny Novikov over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Vladimir Gratinskiy
Category:
Bridge
Target version:
0.2
Start date:
09/21/2017
Due date:
09/22/2017
% Done:

100%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

I don't know how crucial is this issue (i.e. is this a representation issue or something is wrong at the database level) because of it seems that proper computational resources are shown for all safe/unsafe/unknown reports which are children of verification reports.

Actions
Copy link
 #1

Updated by Vladimir Gratinskiy over 7 years ago

I can't find any problems - on verification report page its resources are shown. In DB there are no verification reports without resources.

Actions
Copy link
 #2

Updated by Evgeny Novikov about 7 years ago

A very little time ago this was so, but now this isn't the case. Here is a temporary example where computational resources aren't shown at the verifier page. But I have a suggestion that this issue can be due to considerable changes in Core.

Actions
Copy link
 #3

Updated by Vladimir Gratinskiy about 7 years ago

  • Due date set to 09/22/2017
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Fixed in fix_8449.

Actions
Copy link
 #4

Updated by Evgeny Novikov about 7 years ago

  • Status changed from Resolved to Closed

I merged the branch to master in 564811c7.

Indeed that wasn't a bug in representation, it was an issue with cache calculation in the lightweight mode. Hopefully, cache recalculation available for in the manager panel helps to get computational resources for verification reports even after they weren't filled correctly originally.

Actions
Copy link

Also available in: Atom PDF