build timer incorrect

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 0.6
    • Affects Version/s: 0.5.2
    • Component/s: Builds
    • None

      Not sure how your average time thing works. Since I used the old beetlejuice files, I think it might be incorrect.

      I've removed all 'failed' builds that marked themselves as successful. Looking through every build in the results page, the shortest build I can find is 52 minutes, the longest being 1304. Yet the average time is 45 minutes.....

      I'll restart the app tonight, then re-index - never got round to it before. Then check again and see if this changes, but I can't see why it would, Also, the rss allbuilds.xml and failedbuilds.xml don't include the beetlejuice builds, but may still contain the deleted builds that were marked as successful even though they weren't.

      any obvious ideas why this would be the case? I can manually calculate it to see, but if the minimum successful build is 52 I don't see how it could drop an average of 45...

              Assignee:
              edwin
              Reporter:
              Riaz Khanmohamed
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified