Project

General

Profile

Bug #18848

Statistics not consistent. # of jobs do not match

Added by Anna Mazzacane almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Target version:
Start date:
01/30/2018
Due date:
% Done:

100%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

Example: Campaign f_eg_v1

  1. Job Efficiency Histogram (1 month) -100 jobs
  2. Campagin f_eg_v1 Job wall_time (1 month) - 168 jobs
  3. Campagin f_eg_v1 Job cpu_time (1 month) - 126 jobs
  4. Campagin f_eg_v1 Job copy_in_time (1 month) - 82 jobs
  5. Campagin f_eg_v1 Job copy_out_time (1 month) - 0 jobs
  6. Info by day (same month) - 170 jobs

Associated revisions

Revision 6b7c9580 (diff)
Added by Marc Mengel almost 2 years ago

last part of fix for #18848

History

#1 Updated by Anna Mazzacane almost 2 years ago

  • Description updated (diff)
  • Assignee set to Marc Mengel
  • Priority changed from Normal to Urgent
  • Target version set to v2_3_0

#2 Updated by Anna Mazzacane almost 2 years ago

  • Status changed from New to Assigned

#3 Updated by Marc Mengel almost 2 years ago

So there were two categories of problems:

  1. we weren't using the right limit to print the results in the page template, in particular if there were two zero bars in the histogram, we left the last two bars off.
  2. we weren't counting the missing elements right -- in one case we were getting the zeros but not the NULL's, and in the other we weren't getting a subquery expanded right by sqlalchemy (it was just rendering "FALSE"), so we were always getting zero unknowns.

I think those are all fixed now. Doing consistency checks on some more projects...

#4 Updated by Marc Mengel almost 2 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

#5 Updated by Anna Mazzacane almost 2 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF