Bug #8962
closedBridge says that components finish in statistics while they are in progress
100%
Description
You can see this issue at the attached picture.
Files
Updated by Vladimir Gratinskiy over 6 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.
Updated by Evgeny Novikov over 6 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.
Updated by Evgeny Novikov over 6 years ago
- Priority changed from Urgent to High
- Target version deleted (
2.0)
This is not very important issue at all.
Updated by Vladimir Gratinskiy over 5 years ago
- Due date set to 07/11/2019
- Status changed from New to Resolved
- % Done changed from 0 to 100
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.