Project

General

Profile

Bug #8962

Bridge says that components finish in statistics while they are in progress

Added by Evgeny Novikov almost 2 years ago. Updated 5 months ago.

Status:
Closed
Priority:
High
Category:
Bridge
Target version:
Start date:
06/18/2018
Due date:
07/11/2019
% Done:

100%

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

Description

You can see this issue at the attached picture.


Files

Screenshot_20180618_134625.png (67.4 KB) Screenshot_20180618_134625.png Evgeny Novikov, 06/18/2018 02:32 PM

History

#1

Updated by Vladimir Gratinskiy almost 2 years ago

I don't see something is wrong on the picture. Some components are finished, because there were finish reports for it. And for such components there is statistic. But others are still waiting for finish report. On the screenshot "Core" is in progress (and doesn't have statistic). Also there can be different component instances, when component has statistic for finished instances while it is in progress.

#2

Updated by Evgeny Novikov almost 2 years ago

Vladimir Gratinskiy wrote:

I don't see something is wrong on the picture. Some components are finished, because there were finish reports for it. And for such components there is statistic. But others are still waiting for finish report. On the screenshot "Core" is in progress (and doesn't have statistic). Also there can be different component instances, when component has statistic for finished instances while it is in progress.

I just dislike that, say, for Core there is "1/1" that assumes that it finishes. Also, this is the case for some other components that are in progress forever.

#3

Updated by Evgeny Novikov almost 2 years ago

  • Target version deleted (2.0)
  • Priority changed from Urgent to High

This is not very important issue at all.

#4

Updated by Vladimir Gratinskiy 11 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved
  • Due date set to 07/11/2019

I don't think it is possible in bridge-3.0 as for components pages there are no resources/instances caches. For job page cache with resources and instances is saved at once, after the report is saved, so the bug is not relevant already.

#5

Updated by Evgeny Novikov 11 months ago

  • Target version set to 3.0
#6

Updated by Evgeny Novikov 5 months ago

  • Status changed from Resolved to Closed

In master.

Also available in: Atom PDF