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

Fix Jenkins perf configurations to adjust for recent wtperf scan changes

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • 3
    • 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

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

              Dates

                Created:
                Updated:
                Resolved: