Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4967

Fix Jenkins perf configurations to adjust for recent wtperf scan changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Sprint:
      Storage Engines 2019-08-12

      Description

      The Jenkins job for long wtperf tests measure the maximum latency seen in each test and plots them. Since the merge of WT-4758 those latencies have been measured at essentially 0. That is very unexpected. That ticket modified wtperf itself only.

      I suspect that either something in that change broke the calculation or format output of the latency information. The Jenkins configuration knows/hard-codes the CSV format column of the data it is looking for. So if that information moved, then the job should be updated.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              donald.anderson Donald Anderson
              Reporter:
              sue.loverso Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: