Project

General

Profile

Bug #8626

Can not compare verification results

Added by Evgeny Novikov about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
Start date:
12/13/2017
Due date:
12/18/2017
% Done:

100%

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

Description

For these jobs 1 and 2 I couldn't compare verification results. Besides, I didn't find any error details in log files.

History

#1 Updated by Evgeny Novikov about 1 year ago

Perhaps this is because of one of the jobs has status Failed. If so, I would like to know is it possible to support comparison of verification results for jobs with any statuses. For instance, sometimes I would like to compare jobs some of which weren't solved at all to see differences in job files.

#2 Updated by Vladimir Gratinskiy about 1 year ago

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

Evgeny Novikov wrote:

Perhaps this is because of one of the jobs has status Failed. If so, I would like to know is it possible to support comparison of verification results for jobs with any statuses. For instance, sometimes I would like to compare jobs some of which weren't solved at all to see differences in job files.

Yeah, this is the reason. I've changed it in branch "fix_8632" together with #8632 and #8384. I don't know what can be wrong with comparison of failed or corrupted jobs. Let's users find out it and report me.

#3 Updated by Evgeny Novikov about 1 year ago

  • Status changed from Resolved to Open

We noticed a corrupted comparison cache when comparing verification results. It seems that this is for any pair of jobs having verification results. Cleaning all caches for all jobs doesn't help.

#4 Updated by Vladimir Gratinskiy about 1 year ago

Evgeny Novikov wrote:

We noticed a corrupted comparison cache when comparing verification results. It seems that this is for any pair of jobs having verification results. Cleaning all caches for all jobs doesn't help.

Last commit in branch "fix_8632" (from 26.12.2017) fixed this problem.

#5 Updated by Evgeny Novikov about 1 year ago

  • Status changed from Open to Resolved

Yes, after that commit I could compare many corrupted verification jobs.

#6 Updated by Evgeny Novikov about 1 year ago

  • Target version changed from 2.0 to 1.0

As far as we postpone Klever version:0.3, let's include this issue there.

#7 Updated by Ilja Zakharov about 1 year ago

  • Status changed from Resolved to Verified

Available since 93bb9af9.

#8 Updated by Ilja Zakharov about 1 year ago

  • Status changed from Verified to Closed

Also available in: Atom PDF